The file /home/frank/.cxoffice/win98/drive_c/Windows/msdownld.tmp/AS01E72B.tmp/advpack.dll is infected with the W32/Magistr.a@MM virus!
Guessing from this: " ... /home/frank/.cxoffice/win98/drive_c/Windows/msdownld.tmp/AS01E72B.tmp/ ..." I would assume you maybe have MS Office or MSIE in CrossOver and that you downloaded something ... or maybe just surfed the web? Voila. It got infected and downloaded the worm. It can't do any harm to your Linux programs, but any Windows *.EXE file inside CrossOver might get infected too.frank392 wrote: I have no idea how my computer got it. but it is in my crossover office
You probably got that one via the w32-codecs package which is needed to playback some closed-source formats. Some of those files originate from Windows and probably one file was infected somehow and got into the package. The guy who packed it (probably some MPlayer developer??) could have done a better job at scanning this stuff .... But then again: Why? The virus won't do anything.Matthyis wrote:The file //usr/lib/codecs/vp31vfw.dll is infected with the W32/Magistr.a@MM virus!
VirtualBox itself won't be hurt ... but the virtual OS running inside could be very well infected.Matthyis wrote:will this affect virtual box?
scorp123 wrote:VirtualBox itself won't be hurt ... but the virtual OS running inside could be very well infected.Matthyis wrote:will this affect virtual box?
In our company we used VMware and VirtualBox to infect virtual Windows machines with backdoors, trojans and viruses for testing purposes and to see how quickly they spread from one virtual Windows to the other (the virtual Windows machines were setup so that they would be in the same virtual LAN).
So yes, if you have a virtual Windows inside VirtualBox it can be attacked by viruses, just like a real Windows installation.
Users browsing this forum: Bing [Bot], viper37 and 6 guests