TDS-3 killing MJ Registry Watcher on startup

Discussion in 'Trojan Defence Suite' started by Morpheus, Jul 6, 2005.

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

    Morpheus Registered Member

    Joined:
    Aug 13, 2003
    Posts:
    45
    Hello folks,

    I recently decided to give MJ Registry Watcher a try after stumbling upon a thread in this forum. I have the latest version at time of posting v1.2.4.2. When I start TDS-3 its first act is to terminate (ZwTerminateProcess according to process guard) the program yet when I scan MJ Registry Watcher TDS-3 does not identify it as a trojan or any sort of Malware.

    Does anyone know why TDS-3 kills this on startup, its perfectly happy if I restart it after TDS-3 has loaded.

    Thanks,

    Morpheus.
     
    Morpheus, Jul 6, 2005
    #1
  2. gottadoit

    gottadoit Security Expert

    Joined:
    Jul 12, 2004
    Posts:
    605
    Location:
    Australia
    Its well known behaviour and has been brought up several times before...

    I know that doesn't answer the why question, but I can't think of a really good reason why it should, I just know that it does
     
    gottadoit, Jul 6, 2005
    #2
  3. Gavin - DiamondCS

    Gavin - DiamondCS Former DCS Moderator

    Joined:
    Feb 10, 2002
    Posts:
    2,080
    Location:
    Perth, Western Australia
    "bug" in the self protection against debuggers and other monitors (API spies, window monitors, lots of things)

    Best put as a bug.. not the desired behaviour
     
    Gavin - DiamondCS, Jul 6, 2005
    #3
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...