Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Incidents
[Top] [All Lists]

RE: DoS worm

Subject: RE: DoS worm
Date: Thu, 21 Oct 2004 02:05:36 -0700
From your description your six machines are now compromised by a random
Trojan being controlled by shaman.exodus.ro - I take it you perhaps took
some capture logs of the SSH connections, the SYN flooding and the SMB
probing? That would be invaluable to knowing whether this is a new SMB
vulnerability or whether the worm simply connects using insecure
administrator passwords.


Thor

-----Original Message-----
From: David Gillett [mailto:gillettdavid@fhda.edu] 
Sent: Wednesday, October 20, 2004 10:48 PM
To: incidents@securityfocus.com
Subject: DoS worm

  Yesterday, someone (we believe it was one of our students)
unplugged a lab Mac from the campus network and plugged in a
PC (laptop, we assume).  Besides whatever the user wanted, it
apparently did three things:

1.  Attempt to open a lot of connections (port 22, SSH) to
shaman.exodus.ro (62.80.109.128), then

2.  Send a SYN flood, spoofing the source address as 0.0.0.0,
to ports 22 and 80 of weed.powered.at (195.149.115.18), and

3.  Probe random addresses in our Class B space (port 445, CIFS);
if it got a connection, it tried various SMB-type things amongst 
which I was able to pick out the string "IPC".  Five other machines
in our space eventually demonstrated similar symptoms.

  I don't know what this beast is.  I infer that #2 is a DoS attack
which is perhaps the purpose of the worm, and that #3 is its spread
vector via the IPC$ share.

  Anybody recognize this?

Dave Gillett



<Prev in Thread] Current Thread [Next in Thread>
  • RE: DoS worm, Thor Larholm <=