win32:crypto - Any advice?

Picked up the following yesterday when running a scan:

Win32:Crypto
c:\WINDOWS\Temporary Internet Files\Content.IE5\EJ2FK3EZ\netsecure[1].jpg
Win32:Crypto
c:\WINDOWS\Temporary Internet Files\Content.IE5\4Z887Q8A\panel_r5_c8[1].jpg\panel_r5_c8[1]
Win32:Crypto
C:\WINDOWS\TEMP\trz21E4.TMP

They seem to be living inside some truly enormous (~1GB) files in my temp folder.

Tried to move them to virus chest, but the operation failed (Don’t have the exact words, but something like: “An error occured during this action. Unable to transfer - this option is only available in win32”). Similarly couldn’t repair either.

Now I could just delete all this stuff but I’ve already done this once and the problem has recurred so I’d rather try and get to the bottom of it.

If this is a virus it doesn’t actually seem to be doing anything much (Although my hard drive is filling up with crud >:(). Housecall has shown the disk to be clean, for what it’s worth. Anyhow, my questions are:

Does this ring a bell with anyone?
Could it be a false alert, if so, how do I tell?
If it is a virus would the Avast cleaner tool be any use (It doesn’t list win32:crypto as something it can fix)?
Any other ideas for tracking it down and killing it?

System: Pentium, windows 95B
Avast: Build 4.1.342, virus definitions fully up to date

Cheers

Please delete everything, Windows allows, inside these folders:

c:\WINDOWS\Temporary Internet Files\Content.IE5
C:\WINDOWS\TEMP\

Probably false alarm

It is OK to delete everything from these content.IE5 files/folders is it? I’m getting warnings about deleting a desktop.ini file, but I can’t see why that should be a problem. (I do, however, require reassurance ;D)

How many places does IE stick stuff!

Cheers

If you feel yourself more comfortable you can leave the desktop.ini, but you do not need to. Or follow the instructions in this link: http://www.shepherd.edu/compserv/prevent/internetch.htm

Ah - I hadn’t twigged the link between content.ie5 and the internet explorer cache. Clearing all that out seems to have sorted it anyway.

Guess it was just a false alarm - thanks anyway Raman.