Bionet.405 trojan

Discussion in 'NOD32 version 2 Forum' started by lvhkyjr2, Apr 4, 2004.

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

    lvhkyjr2 Registered Member

    Joined:
    Jan 13, 2004
    Posts:
    37
    this win32/bionet.405 trojan comes up in my virus scans and cant be cleaned cuz in system memory and wont go away and everytime I reboot and nod32 starts up I get a system clock wrong pop up from nod, why cant I delete this?
     
  2. sir_carew

    sir_carew Registered Member

    Joined:
    Sep 2, 2003
    Posts:
    884
    Location:
    Santiago, Chile
    Hello,
    If a malware is active on memory, you need to run Windows in safe mode and then run a full system scan. Every file that NOD found as infected try to clean and if it isn't possible delete them. Most trojans can't be cleaned, because the file is the whole body of the trojan and doesn't contain any valid or usefull information.
    Note: Try to run NOD32.EXE with /ah command, so NOD will detect new and even unknown worms/trojans using Advanced Heuristic.
     
  3. lvhkyjr2

    lvhkyjr2 Registered Member

    Joined:
    Jan 13, 2004
    Posts:
    37
    tryed all that and did'nt work, downloaded trojan hunter and that couldnt clean it also, so I dont know how to get rid of it
     
  4. sig

    sig Registered Member

    Joined:
    Feb 9, 2002
    Posts:
    716
    Try TDS. Just update the database from the site prior to running a scan.
     
  5. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Try running Nod in "Safe Mode"

    Cheers :D
     
  6. lvhkyjr2

    lvhkyjr2 Registered Member

    Joined:
    Jan 13, 2004
    Posts:
    37
    nod in safe mode didnt work , but TDS did
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.