Signature Win32/Genetik cause too many FPs

Discussion in 'ESET NOD32 Antivirus' started by viruscraft, Apr 20, 2008.

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

    viruscraft Registered Member

    Joined:
    Sep 22, 2007
    Posts:
    114
    I'm a moderator of the forum set up by version2 ,the agent of ESET in China.

    I have seen lots of NOD32 users complain about the FPs and most FPs are cause by signature Win32/Genetik.

    More specifically, some normal apps are detected as "probably a variant of Win32/Genetik " frequently.

    IMO,ESET should balance the FPs and the improving of detection rate brought by signature Win32/Genetik ,then make some changes.

    Any aother ideas?
     
  2. lucas1985

    lucas1985 Retired Moderator

    Joined:
    Nov 9, 2006
    Posts:
    4,047
    Location:
    France, May 1968
    It would be helpful if you name what "common apps" are being wrongly detected.
     
  3. omnibus

    omnibus Registered Member

    Joined:
    Apr 20, 2008
    Posts:
    1
    One example is Mailwasher Pro 6.0. It's an installation exe file that has been on my computer since september 2007 and now NOD32 starts giving warnings about the file.
     
  4. ASpace

    ASpace Guest

    Hi!

    What version of Mailwasher do you write about ?

    I just downloaded 6.0.4 and got no warning about it.

    Submit information about it to samples@eset.sk
     

    Attached Files:

  5. viruscraft

    viruscraft Registered Member

    Joined:
    Sep 22, 2007
    Posts:
    114
    Well,there are so many wrongly detected apps and I can not list all of them.

    Recently,a file of P2P downloading software called "Funshion" is detected as "probably a variant of Win32/Genetik " and then deleted so that users can not use it anymore.

    This is the offical website of funshion:
    http://www.funshion.com/english/index.html

    And the report of Virustotal:
    http://www.virustotal.com/zh-cn/analisis/2304db36a0187e574a4c5d378108d3b7

    The most important is that ESET is inefficient in solving FPs.
    When I report a PF,it will take 2-3 days for ESET to fix it.
     
Thread Status:
Not open for further replies.