Windows 7: Trojan: Win32/Bumat!rts detected from ImgBurn

So, I was formatting my computer and reinstalling today and I went to the ImgBurn website and downloaded from their "preferred mirror" from BetaNews..it was the 1st mirror listed.

Upon install, MSE went off and detected Trojan: Win32/Bumat!rts and stopped it in it's tracks.



Another example, of common sense not being enough to protect you.

I got ImgBurn from the second mirror and all is well.

Ohh that's strange.

Yeah, there is nothing like being 40 minutes into a build where you typically only install about 10 things and having something fishy already going on.

Guess I'm just happy that I put MSE on there prior to the rest of this stuff.

Norton doesn't detect anything on the file from BetaNews.

I don't use K-Lite Codec Pack anymore but two people at the Norton forums were reporting that the latest version (at the time) was setting SONAR2 off. I downloaded the exact same file from the exact same address but I was able to run the installer without SONAR2 going off. All my settings are set to high.

It's possible that they either fixed it...or the Mirror has a collection of load balanced servers and one of them is compromised.

Yeah, I realise that.

BetaNews, like others in its kind, hosts few bad files and links to one suspicious domain.

I got a Mcafee warning Artemis! trojan, and it deleted the installer automatically. Is this a false+?

(I downloaded it from the recommended free software page here at 7forums.)

No virii on Linux...

Please... Let's not start this tirade here. It's counter productive and not necessary.

You think that's fishy. I worked for a hospital once where our user's had to send personal health information to the state. To do this, they used an intermediary network provider (a huge company, which I hesitate to say their name, but it rhymes with BT&T). They simply provided a secure connection the states' systems.

One day, suddenly, every single time our user's would connect, our Enterprise AV would warn of a Conficker virus and would supposedly stop it. I personally wrote the IT guys at this conglomerate and warned them that their servers (the infection came once connected to the secure appliance, but before reaching the state systems) appeared to be infected with Conficker, but they basically told us to mind our own business.

Lo and behold, about two weeks later, we had a major outbreak of Conficker, which we had to spend a long time cleaning up and investigating. And guess where it came from!

Even trusted sources can be compromised.