Sockets De Trois V1

From: Gary Brett (globalg2001_at_yahoo.co.uk)
Date: 10/31/03

  • Next message: Duane Arnold: "Re: BlackICE Uninstall/Install problems!!!" 
    Date: 31 Oct 2003 02:07:02 -0800

    After running GSNetScan I discovered I had a "Sockets De Trois V1"
    trojan on all my LAN XP Pro machines. I have since closed port 5000 on
    the Firewall and have disabled "SSDP Discovery Service" in WinXP
    Services. This seems to have stopped the Trojan, but do you know how
    it entered the LAN and what it actaully does when inside. Presumably I
    have not destroyed it by closing the ports, just halted its progress?

    Thanx for your time..

    Gary

  • Next message: Duane Arnold: "Re: BlackICE Uninstall/Install problems!!!"

    Relevant Pages

    • Re: Sockets De Trois V1
      ... I have since closed port 5000 on ... This seems to have stopped the Trojan, ... > it entered the LAN and what it actaully does when inside. ... that with port 5000 open, it's possible one reason could be Sockets de Trois ...
      (comp.security.firewalls)
    • Re: Sockets De Trois V1
      ... > and closed port 5000 on the firewall which seems to have done the ... > trick but I still want to know how the bugger got it to my LAN. ... > caught the Trojan.. ...
      (comp.security.firewalls)
    • Re: Databaseben, I sent you a message below
      ... your discovery. ... remember that a trojan by design hides ... on the other posting is referring to an explorer ... all of them kept asking me if i wanted a toolbar. ...
      (microsoft.public.windowsxp.help_and_support)
    • Re: ICMP - What the hell are these log files telling me.....
      ... to reduce the log files do you think? ... De Trois V1" trojan on all my LAN XP Pro machines. ... port 5000 on the Firewall and have disabled "SSDP Discovery Service" ...
      (comp.security.firewalls)
    • Re: ICMP - What the hell are these log files telling me.....
      ... > it is a good idea to limit 'em in case you're flooded with ICMP ping, ... >> in WinXP Services. ... >> know how it entered the LAN and what it actaully does when inside. ... caught the Trojan.. ...
      (comp.security.firewalls)