I decided to run a full Defence+ scan with CFP earlier today while I was out for a couple of hours. When I returned back, not only had it found something suspicious, the scanner was “stuck” on a file, using excessive CPU.
Technical stuff:
I’m using Windows XP, SP3, with latest Windows updates. The only security application I use is CFP3 (3.0.25.378), updated just before the scan. Symptoms:
a) Malware found: “C:\I386\WEXTRACT.exe” (id = 0xb2ebe)
b) “Elapsed time”-counter stopped at 1+ hour something, but the magnifier scanner symbol animating as if it was still scanning (it said it was now scanning “C:\WINDOWS\Ökensand.bmp”, Ö being the last letter in my national alphabet and “Ökensand” the last file in the Windows folder).
c) cfpconfig.exe was using up to 70-80% CPU, even after stopping the scan and closing the scanner window.
Now, a google search for Wextract.exe tells me that it’s the legitimate Microsoft “Win32 Cabinet Self-Extractor”, but this file should normally not exist in the C:\I386 folder. There is no visible wextract process running on my computer, and I have never recieved a warning about it previously. An upload of the file to virustotal.com gives no malware return. I would think it’s a false positive, but why would the Defence+ scanner think it’s some kind of malware? Istn’t CFP3 using the upcoming CIS engine in it’s scanner?
On a sidenote, the behaviour of the scanner as described in b) and c) above was a bit strange, but I guess it has nothing to do with the wextract.exe?