BugTraq
Re: Outbreak warning: possibly Mydoom.C (Now Deadhat/Vesser) Feb 09 2004 06:01PM
K-OTiK Security (Special-Alerts k-otik com) (3 replies)
Re: Outbreak warning: possibly Mydoom.C (Now Deadhat/Vesser) Feb 09 2004 11:04PM
Mary Landesman (mlande bellsouth net)
Re: Outbreak warning: possibly Mydoom.C (Now Deadhat/Vesser) Feb 09 2004 07:21PM
Nick FitzGerald (nick virus-l demon co uk) (1 replies)
RE: Outbreak warning: possibly Mydoom.C (Now Deadhat/Vesser) Feb 09 2004 10:02PM
Larry Seltzer (larry larryseltzer com) (2 replies)
RE: Outbreak warning: possibly Mydoom.C (Now Deadhat/Vesser) Feb 10 2004 08:46PM
Nick FitzGerald (nick virus-l demon co uk)
Re: Outbreak warning: possibly Mydoom.C (Now Deadhat/Vesser) Feb 10 2004 09:12AM
Gadi Evron (ge linuxbox org)
> They all have it as a low-incidence in the wild. What I don't understand is that if it
> hasn't spread, what caused the attack against Microsoft this morning?

A worm that spreads this way can't become huge for obvious reasons, but
it still spreads, thus the DDoS against MS.

There is a some (naming) confusion in the different vendor web pages
about this worm, but the interesting part is that Mydoom.A's source code
is included.

Gadi

[ reply ]
Re: Outbreak warning: possibly Mydoom.C (Now Deadhat/Vesser) Feb 09 2004 07:00PM
Gadi Evron (ge linuxbox org)


 

Privacy Statement
Copyright 2010, SecurityFocus