The Latest from The Mozy Blog: What's new with Mozy?
A couple new updates have been released for the Windows and Mac clients as well as some new features in the latest Linux client. Check out our latest blogs for all the details!
Shuriken malware in Mozy file detected by Bitdefender
For the last few days, Bitdefender said it found Shuriken malware in a file named MOZY-2_26_3_393-58496.EXE. Each time, I've quarantined and deleted this file (although I'm not sure if the file name is exactly the same each time), but it keeps coming back.
I'm going through Bitdefender forum to see if they have a solution.
I've never hear of one of our .EXE setup files being flagged by an antivirus or anti-malware program but that doesn't mean that the file hasn't been changed or modified by a virus or malware program.
You say that you have deleted the file, but was that delete procedure done through the Bitdefender or directly on the file in Windows Explorer? I would attempt to delete the file directly in Windows File Explorer if you haven't already using the "Shift" key + Delete to delete the file without sending it to the recycle bin.
If the file keeps coming back as you say it has then I would run a "full scan" using Bitdefender to make sure it searches the entire computer for a possible virus or malware.
Also if the file keeps returning even after running a full scan using Bitdefender then you may want to try using a different antivirus / malware program to search.
I once had McAfee running on my home computer and got a virus that it could not "clean" that Norton antivirus was able find and get rid of.
Re: Shuriken malware in Mozy file detected by Bitdefender
Thanks for your response.
First of all, I mistakenly said that Bitdefender found the malware, when it was actually Malwarebytes. (I confused the two because of an unrelated issue with Bitdefender.)
After my original post, I looked at Malwarebytes' reports, because the malware was getting flagged 3-4 days in a row -- even though Malwarebytes said it was deleted each time. The reports said "removal failed."
Anyway, I was able to find the malware file and deleted (using shift-delete).