Strange BOClean issue

Discussion in 'other anti-trojan software' started by HURST, Sep 10, 2007.

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

    HURST Registered Member

    Joined:
    Jul 20, 2007
    Posts:
    1,419
    Hi

    since I installes boclean a few days ago, I had the same problem twice. I connect over WiFi, and connections looks good, can browse the web, but it appears as it would be still resolving IP address. In the wireless client (intel 3945), the IP is already fine, but the windows wireless icon in the tray keeps trying to resolve it. As I said, I can browse normally, but MSN messenger doesn't connect.

    First time this happened, I didn't knew why this happened, and performed a System Restore to the day before. This solved the issue. The problem happened after BOClean found a trojan, disabled it and removed the file, but I didn't thought this was the cause until today, when I had the same problem, after BOClean removed another file (This time an anti-keylogger test).

    Anyone had the same issue? anyone know how to solve it? I certainly don't wanna perform System Restore every time BOClean finds anything, and I don't wanna loose BOClean neither.
     
  2. Perman

    Perman Registered Member

    Joined:
    Nov 23, 2005
    Posts:
    2,160
    Hi, folks: Where is this trojan which BOC has spotted located?
     
  3. HURST

    HURST Registered Member

    Joined:
    Jul 20, 2007
    Posts:
    1,419
    The first time it was a trojan found in some keygenerator I downloaded for testing purposes. It was in the Incoming folder from eMule, and was terminated by boclean when executed.
    Today's was in an anti-keylogger test I had downloaded to my desktop.

    I have the report for the second one.

    ------------------------------
    09/10/2007 12:54:45: AKLTKEYLOG VARIANT STOPPED BY BOCLEAN!
    Trojan horse was found in memory.
    C:\DOCUMENTS AND SETTINGS\TOMAS J. KING\ESCRITORIO\AKLT.EXE contained the trojan.
    Active trojan horse WAS shut down. System safe.
    Logged in user: Tomas J. King
     
  4. HURST

    HURST Registered Member

    Joined:
    Jul 20, 2007
    Posts:
    1,419
    Solved it unchecking "Automatic cleanup of winsock connectivity"

    Thanks
     
  5. Perman

    Perman Registered Member

    Joined:
    Nov 23, 2005
    Posts:
    2,160
    Hi, folks: Good work. There are quite few similar incidents like yours earlier. Also there are warnings from BOC' web site regarding to this.
     
Thread Status:
Not open for further replies.