Boclean alert after latest update

Discussion in 'other anti-trojan software' started by snowbound, Dec 18, 2007.

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

    snowbound Retired Moderator

    Joined:
    Feb 18, 2003
    Posts:
    8,723
    Location:
    The Big Smoke
    Just wanted to enquire if anyone here may have encountered this after the latest update of Boclean,

    DLDR-AGENT.AQF MALWARE STOPPED by BOCLEAN!
    Trojan horse was found in memory.
    C:\WINDOWS\SYSTEM32\USERINIT.EXE contained the trojan.
    Active trojan horse WAS shut down. System now safe.

    I received it a few moments ago.

    There is already a thread started with this issue at the Comodo forums,

    http://forums.comodo.com/empty-t17328.0.html;msg118609




    snowbound
     
    snowbound, Dec 18, 2007
    #1
  2. jiskefet

    jiskefet Registered Member

    Joined:
    Dec 17, 2007
    Posts:
    16
    Location:
    Friesland
    Yep, i have the same issue.
     
    jiskefet, Dec 18, 2007
    #2
  3. Huupi

    Huupi Registered Member

    Joined:
    Sep 2, 2006
    Posts:
    2,024
    Same here o_O
     
    Huupi, Dec 18, 2007
    #3
  4. subferno

    subferno Registered Member

    Joined:
    Oct 3, 2004
    Posts:
    92
    Me 2. This is the second time I got a possible False Positive from Comodo BOClean. I wonder if I should move on to something else.
     
    subferno, Dec 18, 2007
    #4
  5. HAN

    HAN Registered Member

    Joined:
    Feb 24, 2005
    Posts:
    2,098
    Location:
    USA
    Apparently fixed with update 2007-12-19 06:19:18
     
    HAN, Dec 19, 2007
    #5
  6. snowbound

    snowbound Retired Moderator

    Joined:
    Feb 18, 2003
    Posts:
    8,723
    Location:
    The Big Smoke
    Took a little longer than i would have liked but... :thumb:




    Steve
     
    snowbound, Dec 19, 2007
    #6
  7. ccsito

    ccsito Registered Member

    Joined:
    Jul 27, 2006
    Posts:
    1,579
    Location:
    Nation's Capital
    Hmm.. you wonder whether the message was a fake alert or if a process was terminated? I guess since no one got a BSOD there was no real issue? :doubt:
     
    ccsito, Dec 19, 2007
    #7
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.
    Accept Learn More...