9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jack Johnson <fragment@nas.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] missing cmd.exe
Date: Wed, 22 Jan 2003 08:33:10 -0800	[thread overview]
Message-ID: <3E2EC7C6.2030906@nas.com> (raw)
In-Reply-To: <3E2EABA3.4070807@strakt.com>

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



      reply	other threads:[~2003-01-22 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-22  2:05 Skip Tavakkolian
2003-01-22 12:25 ` Anthony Mandic
2003-01-22 14:33   ` Boyd Roberts
2003-01-22 16:33     ` Jack Johnson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E2EC7C6.2030906@nas.com \
    --to=fragment@nas.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).