M
marek jedlinski
Funny thing happened. I've used the freeware AntiVir for some time, but for
some reason I've always held on to the DOS-based free version of F-Prot.
Somehow I always had high regard for F-Prot, perhaps because it was one of
the first, if not _the_ first scanner to work with Word macro viruses back
when they first appeared (it was a separate commandline program then),
perhaps also because they have a Linux version, all that.
So last night I went and bought F-Prot for Windows, partly because I
vaguely believed it was going to be at least as secure as AntiVir, and
partly because the GUI is such an eye-candy (heh, yeah, I know...) I also
downloaded the latest update.
Today I had to uninstall the firewall. In the 20 minutes between
reinstalling it, I got infected with Randex.D (or a variant - the trojan
that sends itself over network shares and places msmsgri32.exe in
winnt\system32 folder). F-Prot was running at the time and didn't so much
as beep. The only indication I got was that Startup Monitor alerted me that
msmsgri32.exe was trying to add itself to the registry in HKLM\Run.
The virus is fairly harmless as viruses go, but F-Prot really dropped the
ball on this one. Even with the most thorough scan settings (identify by
content, heuristics, neural) it doesn't recognize msmsgri32.exe as a virus
at all. I sent the file to F-Prot, but this virus has been known since
August 2003, so it's not new at all.
I went back to AntiVir and sure enough, the guard didn't even let me unpack
the executable from a zipfile when I wanted to test it. So, did I just blow
$29 for the pretty interface? Should I stick with AntiVir?
(Before today, I'd only ever had one virus on my machine, back in the days
of MS DOS 3.13 or so. I didn't think I actually needed a scanner
..marek
some reason I've always held on to the DOS-based free version of F-Prot.
Somehow I always had high regard for F-Prot, perhaps because it was one of
the first, if not _the_ first scanner to work with Word macro viruses back
when they first appeared (it was a separate commandline program then),
perhaps also because they have a Linux version, all that.
So last night I went and bought F-Prot for Windows, partly because I
vaguely believed it was going to be at least as secure as AntiVir, and
partly because the GUI is such an eye-candy (heh, yeah, I know...) I also
downloaded the latest update.
Today I had to uninstall the firewall. In the 20 minutes between
reinstalling it, I got infected with Randex.D (or a variant - the trojan
that sends itself over network shares and places msmsgri32.exe in
winnt\system32 folder). F-Prot was running at the time and didn't so much
as beep. The only indication I got was that Startup Monitor alerted me that
msmsgri32.exe was trying to add itself to the registry in HKLM\Run.
The virus is fairly harmless as viruses go, but F-Prot really dropped the
ball on this one. Even with the most thorough scan settings (identify by
content, heuristics, neural) it doesn't recognize msmsgri32.exe as a virus
at all. I sent the file to F-Prot, but this virus has been known since
August 2003, so it's not new at all.
I went back to AntiVir and sure enough, the guard didn't even let me unpack
the executable from a zipfile when I wanted to test it. So, did I just blow
$29 for the pretty interface? Should I stick with AntiVir?
(Before today, I'd only ever had one virus on my machine, back in the days
of MS DOS 3.13 or so. I didn't think I actually needed a scanner
..marek