trojan in backup file?

I have just begun using Paragon Backup & Recovery 10 Free Edition. I have an Asus Eee on which I've recently re-installed Windows XP (from disk image on CD-ROM that came with the computer). That install was followed by installing of Windows updates, installing of Avast5, and installing of various utilities and applications from original CDs, Download.com, and SourceForge.net. I then used Paragon to make a backup to a folder on an external HD. I use this external HD for various data files and backups, so I scan it weekly. Today I scanned it with Avast5 and got a warning for one of the files in the backup folder created by Paragon:

High Threat: Win32:Hupigon-ONX[Trj]

I then used Avast5 to scan the Asus Eee, and got a clean scan. As best I can recall, I haven't deleted anything from the Asus since I made the backup. So I am wondering, do I have a trojan in my backup? If so, how did it get there?

 

It seems that his particular scenario has been around for some time with Avast and various image files.You might wish to follow this thread:

http://forum.avast.com/index.php?PHPSESSID=eb8976131d9b7b15bda03f459c82ab1a&topic=57768.0

Also this thread details a similar problem:

http://forum.avast.com/index.php?topic=58206.0

It does seem to be a FP given that no other scanner tried has flagged anything,unlikely after an extended period of time if it was malware.

 

Thanks for the links. Sure does sound similar. However, to clarify, the backup is recent and this was the first scan I have done of the external HD since I made the backup. So the file in question has not been present for an extended time or been checked by other scanners.

To be on the safe side, I have deleted the backup in question. I will do thorough scans of the Asus itself. If these come up clean, my next move will be to defrag the Asus, scrub the free space, then make another backup and scan that. Since I have a heavy workload right now and the Asus is not my primary machine, it will probably take me several weeks to complete the process. In the meantime, I will gladly read any additional comments folks may have.

 

Sorry,what I meant was that the similar issues referenced have been around for some time,not meaning your particular detection.I hesitate to say that it's definitely a FP,but on balance it would seem to be.You took the safest option in deleting that particular image just in case.It'll be interesting to see if you get any subsequent detections when scanning other images.

 

on the balance of probabilities i also think it was an FP rather than some malware