Joel
Newbie


Gender: 
Posts: 34
|
 |
Re: Warning msg, "Unable to unpack upx-packed file
« Reply #6 on: May 7th, 2003, 9:22pm » |
Quote Modify
|
Hank, You've stumbled on a complicated one here. I'm going to give you a tiny bit of background that will help you to understand what is happening. It may help you to find out why it is happening. When TH goes to scan a compressed file, like a ZIP or an RAR or these UPX things, it needs to un-compress the file or extract it, in order to look at the actual files that are inside it. It has to put these un-compressed files somewhere while it is scanning them, so it asks Windows where to put temporary files. That is where it is getting that long directory string from. The one with the ~1 stuff in it. The reason you can't usually find the file by the part just at the end is that when Windows looks for files, it doesn't try to un-compress and extract them all to see what it inside them, so it isn't seeing the individual file(s) that TH is complaining about. Now, all TH is saying is that it can't figure out how to unpack that particular file. It isn't actually saying that there is anything bad with the file, because it can't even get far enough to see what the file really says. If you had a trojan running, it would need to be sitting in memory while it is running, and TH scans your memory for nasties, and it isn't finding anything nasty running. So while you still need to try to figure out what the source of this file that can't be unpacked is, and send it in to Magnus so he can take a look at it, in case it is a new trojan, you don't have exidence of anything running in memory that TH is aware of at this time. The port issue may be unconnected. I think the only way you may be able to find the offending file is to continue what you started. You isolated it to a scan on your F drive, if I remember from above. Next, try scanning one folder at a time on your F drive. When you find the folder that gives the unpack warning, scan each subfolder or file. Etc. NOTE TO MAGNUS: Could you add a feature that would indicate the original file name that contains the file TH can not unpack? As you can see, the literal name of the unpackable file doesn't help anyone if it is in some sort of larger compressed file, etc.
|