From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3E2EC7C6.2030906@nas.com> From: Jack Johnson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2a) Gecko/20020910 MIME-Version: 1.0 To: 9fans@cse.psu.edu Subject: Re: [9fans] missing cmd.exe References: <166961a912968c8026ef0deac2c4f0a6@centurytel.net> <3E2E8230.914E3F15@start.com.au> <3E2EABA3.4070807@strakt.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 22 Jan 2003 08:33:10 -0800 Topicbox-Message-UUID: 45de4b62-eacb-11e9-9e20-41e7f4b1d025 Boyd Roberts wrote: > Anthony Mandic wrote: > >> It shouldn't be too hard to develop a script or program >> called cmd.exe to do something fun. I'm surprised Boyd >> hasn't suggested this yet ... >> > On reflection, something like Ches' 'jail' would be a cool trick, > but maybe a lot of work. If you do some checking with Google, you'll find that some people have done a number of things on various operating systems when they see these kinds of requests come through. The more interesting (I think) are the ones recognized as the IIS codered worm, because if they're knocking on your door it means they're already infected, which gives you some more information about the host system. There's a pretty popular script floating around to pop up a notification window on the infected host with a warning to the owner that they've been infected, along with a handy URL to find out more info. Others noted that it might be a headless box in a closet somewhere, so have attempted to modify the script to broadcast a message to the local domain/workgroup to let anyone/everyone know that the host is infected. Some people have attempted to write scripts which go back and kill the worm on the infected host. Here's a random example (Googled): http://salfter.dyndns.org/codered.shtml Please note that exploiting an infected host to notify the owner of its infection is probably illegal in the United States and any country willing to buy U.S. goods rather than produce them. -Jack