if it infected a legitimate file nod would have called it a virus
instead... since it didn't call it a virus and since it's so old and
part of a legitimate application suite i rather suspect it's a false
alarm - unless you've sent in to nod and they've confirmed that it is
indeed the trojan their product says it is...
.. . . and thats exactly what happened (i.e., NOD didn't call it a
virus, its an old file part of a legitimate application and after
sending it to NOD they say it is a trojan). Now this is where I think it
gets more interesting. I've been using NOD32 for over 2 years and it
didn't detect it until very recently. The following links would suggest
that this is an issue that has recently cropped up with MGI PhotoSuite
and some versions of Print Shop Deluxe
http://www.broadbandreports.com/forum/remark,10248589~mode=flat
http://www.broadbandreports.com/forum/remark,10187617~mode=flat
Was this file inserted in these products for some reason and are some of
the AV products only now detecting it? I'll try uninstalling and
reinstalling MGI PhotoSuite from the CD and see if that results in any
detection changes. I'm still looking for a URL by the way with a
definition for this trojan.
This issue is starting to bring back memories of an old "Buggy.Shell"
problem McAfee used to detect on a Compaq Presario I had a few years
back. Seems it thought that a file related to a mouse tutorial was
transmitting sensitive information.
Denney