BUG: Super AntiSpyware is not a trojan.

Discussion in 'ESET NOD32 Antivirus' started by jordana, Jun 8, 2009.

Thread Status:
Not open for further replies.
  1. jordana

    jordana Registered Member

    6/8/2009 9:01:28 AM - Module Startup scanner - Threat Alert triggered on computer xxxxxxx: C:\Program Files\SUPERAntiSpyware\SUPERAntiSpyware.exe contains probably a variant of Win32/Genetik trojan.

    We use SuperAntispyware on a couple hundred computers here, and have for a few months now. It picks up A LOT of spyware that Nod32 misses.

    Please fix this,
  2. Thankful

    Thankful Registered Member

    Please provide the following:
    1. Operating System with service packs
    2. NOD32 version number
    3. Version of virus signature database
    4. Version of SuperAntispyware with database version.
  3. lodore

    lodore Registered Member

    copy the file to somewhere and zip it up in an archive with the password virus email to samples[AT]eset.com or sample[AT]eset.com with the subject FP and put a little bit of detail in the body of the email.

    I will see if i can get hold of someone from superantispyware and send them the link to your post.
    Last edited: Jun 8, 2009
  4. Thankful

    Thankful Registered Member

    I'm running SuperAntispyware Free without any problem.
  5. rj104

    rj104 Registered Member

    Just had exactly the same problem after Nod updated.

    OS: Windows XP Professional

    Nod V 4.0.424.0
    Update 4139 (2009060:cool:
  6. funkydude

    funkydude Registered Member

    Maybe you are running outdated copies of SAS?
  7. Thankful

    Thankful Registered Member

    Just ran a full scan with all parameters checked using sig. 4139, NOD32 4.0.437.0, no alert. I'm running SuperAntispyware Free 4.26.1004, defs updated 6.8.09 at 3:30 PM Eastern Time Zone. Running Windows XP Pro, SP3.
    Maybe the Pro version of SuperAntispyware is causing the FP?
  8. Thankful

    Thankful Registered Member

    What version of SuperAntispyware are you running?
  9. Banger696

    Banger696 Registered Member

    I had the same today after a regular deep scan but not on other computers. Re-installed SAS all fixed. *puppy*
  10. T-RHex

    T-RHex Registered Member

    It happened with 4.25.1012 of the free edition, so it wasn't Pro only.
    I only update SAS to run a scan once every couple of months, so I had a couple of PCs come up with a threat alert on this. However, it looks like ESET fixed it, as I rescanned with the latest virus defs (4143/20090610) and no threat was found.
Thread Status:
Not open for further replies.