FP, submitted multiple times, and still killed by Nod32

Discussion in 'ESET NOD32 Antivirus' started by softtouch, Jan 9, 2010.

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

    softtouch Registered Member

    Joined:
    Jan 31, 2006
    Posts:
    415
    Eset kills our program on users pc's because of a FP.
    It was submitted multiple times, and its still killed all the time.
    Our clients are screaming at us. They should scream at Eset...
    Eset is (beside one China AV) the only one at VT who detect it.
    How long will it usually take until a FP is corrected?
    We update at least once/day, does that mean I will have to tell our customer to ditch Nod32 and get something else?
     
  2. buckZor

    buckZor Registered Member

    Joined:
    Dec 9, 2009
    Posts:
    14
    Location:
    Peoples Republic of Oregon
    Not to be quip, but ever heard of the concept of exclusions?
     
  3. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    Last edited: Jan 10, 2010
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    You didn't mention how the application is detected. Is it detected as a NewHeur_PE virus, Themida, etc.? Did you submit the FP per the instructions here?
     
  5. softtouch

    softtouch Registered Member

    Joined:
    Jan 31, 2006
    Posts:
    415
    Sorry, forgot to mention that.

    Its detected as "probably a variant of Win32/Genetik"

    And a couple of users submitted it. I also submitted it multiple times.

    I got this morning an email from ESet:

    ~Private communication removed per the TOS.~


    But until this email arrived, we created already 2 new updates, which of course are again flagged...

    I cannot tell thousands of users to exclude it. Vt shows always 2/41 for me, one is Nod32, the other is a Chinese AV which detects just everything as suspicious.

    Is there anything we can do that ESet will stop flagging it?
    Its a legit application, digitally signed by me, and I have no clue whats the cause that it gets flagged.
     
    Last edited by a moderator: Jan 10, 2010
Thread Status:
Not open for further replies.