Found a trojan

Discussion in 'NOD32 version 2 Forum' started by olaha, Apr 17, 2005.

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

    olaha Registered Member

    Joined:
    Apr 15, 2005
    Posts:
    19
    I just ran an in depth analysis (an option I hadn't noticed before...) and found a trojan (phishing.gen trojan). Isn't it strange that it manage to get past NOD32 in the first place. Why wasn't it detected by my scheduled weekly scan (NOD32 - scanning)? I'm using NOD32 2.12.3.
     

    Attached Files:

  2. dvk01

    dvk01 Global Moderator

    Joined:
    Oct 9, 2003
    Posts:
    3,131
    Location:
    Loughton, Essex. UK
    It was probably in the temp internet files from some time ago & NOD has only just added detection for that version of it

    1) Open Control Panel
    2) Click on Internet Options
    3) On the General Tab, in the middle of the screen, click on Delete Files
    4) You may also want to check the box "Delete all offline content"
    5) Click on OK and wait for the hourglass icon to stop after it deletes the temporary internet files
     
  3. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    HTML Phising trojans merely contain pure text. They are actually deceiving emails which pretend to be sent from a bank authority in order to get details about the recipient's account details etc.
     
  4. maxim

    maxim Guest

    Eeek, Nod32 found that trojan in a 700MB movie i just downloaded so i deleted it all! Have i deleted a perfectly good movie?
     
  5. NOD32 user

    NOD32 user Registered Member

    Joined:
    Jan 23, 2005
    Posts:
    1,766
    Location:
    Australia
    :)
    Perhaps, but in any case, I'm sure it wouldn't have been a perfectly legitimate movie :)
     
  6. The Hammer

    The Hammer Registered Member

    Joined:
    May 12, 2005
    Posts:
    5,619
    Location:
    Toronto Canada
    Sounds like you avoided a horror film. ;) :D
     
    Last edited: Oct 6, 2005
Thread Status:
Not open for further replies.