N
null
A freeware MP3 to WAV installation file named ABLEMP3.EXE from:
http://www.all4you.dk/FreewareWorld/links.php
was found to contain a file named WU1345RD.EXE infested with
TrojanDropper.Win32.Small.gt
Actual infestation was confirmed by Kaspersky Lab virus analysis.
I ran some tests using updated av products set to scan archives and
packed files. I wanted to see which scanners could find the Trojan in
the installation SFX CAB file. Of the scanners I tried, only KAV (and
KAV scan engine products) and BitDefender found the culprit file and
alerted.
Scanners which alerted on the culprit file but not on the installation
file included:
F-Prot
McAfee
AntiVir
Clamav
NOD32
Scanners which had no detection at all included:
Trend's Sysclean
Norman Virus Control (NVC)
In this particular case, the SFX CAB installation file can be handled
by Archivers such as Power Archiver. The files "within" can be
extracted to a temp folder. Then the temp folder and its
subdirectories can be scanned with the culprit file(s) exposed for av
scanning.
A general fault of the scanners that can't handle the "containers"
(archivers and packers) is that they report "OK", giving uninitiated
users the impression that the file is safe to Run. In fact, the "files
within" a install file may be packed in a way that some scanners can't
handle. And again, you get a "OK" message. I have seen KAV give
reports such as "unknown" or "error on" and similar for some of these
situations, so apparently it's trying to be honest and let the user
know it can't scan a file. But honesty in reporting is a very rare
thing indeed
Art
http://www.epix.net/~artnpeg
http://www.all4you.dk/FreewareWorld/links.php
was found to contain a file named WU1345RD.EXE infested with
TrojanDropper.Win32.Small.gt
Actual infestation was confirmed by Kaspersky Lab virus analysis.
I ran some tests using updated av products set to scan archives and
packed files. I wanted to see which scanners could find the Trojan in
the installation SFX CAB file. Of the scanners I tried, only KAV (and
KAV scan engine products) and BitDefender found the culprit file and
alerted.
Scanners which alerted on the culprit file but not on the installation
file included:
F-Prot
McAfee
AntiVir
Clamav
NOD32
Scanners which had no detection at all included:
Trend's Sysclean
Norman Virus Control (NVC)
In this particular case, the SFX CAB installation file can be handled
by Archivers such as Power Archiver. The files "within" can be
extracted to a temp folder. Then the temp folder and its
subdirectories can be scanned with the culprit file(s) exposed for av
scanning.
A general fault of the scanners that can't handle the "containers"
(archivers and packers) is that they report "OK", giving uninitiated
users the impression that the file is safe to Run. In fact, the "files
within" a install file may be packed in a way that some scanners can't
handle. And again, you get a "OK" message. I have seen KAV give
reports such as "unknown" or "error on" and similar for some of these
situations, so apparently it's trying to be honest and let the user
know it can't scan a file. But honesty in reporting is a very rare
thing indeed
Art
http://www.epix.net/~artnpeg