Virus From Spybot S & D

  • Thread starter Thread starter Radio Man
  • Start date Start date
R

Radio Man

Three times i tried downloading the latest version
of Spybot S & D & i get the following virus:

Win32/Adware.Alexa Application

The file name is:

C:\Program Files\Spybot-Search & Destroy\Dummies\is-8143C.tmp

Is there a solution to the above problem?
 
Radio said:
Three times i tried downloading the latest version
of Spybot S & D & i get the following virus:

Win32/Adware.Alexa Application

The file name is:

C:\Program Files\Spybot-Search & Destroy\Dummies\is-8143C.tmp

Is there a solution to the above problem?
Click to expand...
What AV product are you using?
-max

--
Keeping Windows Clean: http://www.geocities.com/maxpro4u/madmax.html
Virus Cleaning+Fixes: http://www.geocities.com/maxpro4u/TechPros
Change nomail.afraid.org to neo.rr.com so you can reply by e-mail
(nomail.afraid.org has been set up specifically for
use in Usenet. Feel free to use it yourself.)
 
Radio said:
Three times i tried downloading the latest version
of Spybot S & D & i get the following virus:

Win32/Adware.Alexa Application

The file name is:

C:\Program Files\Spybot-Search & Destroy\Dummies\is-8143C.tmp

Is there a solution to the above problem?
Click to expand...
False positive in NOD32. That is the AV that is giving you this message,
correct?
 
I had a file in Spybot S&D also in the same location named
"dummy related.htm" that read infected by Nod32.
I just tested it at the virustotal website
http://www.virustotal.com and the results were blank - meaning no
infection.

Netuser 58
 
The new update from Nod 32 corrects that error. I retested the file
with Ammon and everything reads OK - no infection.

Netuser 58
 
Netuser said:
I had a file in Spybot S&D also in the same location named
"dummy related.htm" that read infected by Nod32.
I just tested it at the virustotal website
http://www.virustotal.com and the results were blank - meaning no
infection.

Netuser 58
Click to expand...
Yes. That's to be expected when it's a *false positive* ;)
 
Netuser said:
The new update from Nod 32 corrects that error. I retested the file
with Ammon and everything reads OK - no infection.

Netuser 58
Click to expand...
See, I found the problem running the NOD32 on demand scanner. But it's
good to know the fix is in.
 
Back
Top