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)
In-Reply-To: <4027B328.4050305 (at) egotistical.reprehensible (dot) net [email concealed]>

it's not mydoom.c - his name is Vesser (W32.HLLW.Deadhat) :

Vesser mainly targets computers that have previously been infected with the Mydoom.A or Mydoom.B worms. Vesser scans for the backdoors in those worms on IP addresses. While doing that it connects to TCP ports 1080. 3127 and 3128 and tries to copy itself there in a specially-crafted package.

http://www.f-secure.com/v-descs/vesser.shtml

http://securityresponse.symantec.com/avcenter/venc/data/w32.hllw.deadhat
.html

Regards.

C. Bekrar - Security Consultant

K-OTik Security (France)

http://www.k-otik.com

>Date: Mon, 09 Feb 2004 18:19:52 +0200

>From: Gadi Evron <ge (at) egotistical.reprehensible (dot) net [email concealed]>

>To: bugtraq (at) securityfocus (dot) com [email concealed]

>Subject: Outbreak warning: possibly Mydoom.C

>

>Uses the Mydoom backdoor to upload itself (over Mydoom ports).

>

>Seeded over the weekend, it is out now and spreads fast.

>

>Blocking: block Mydoom ports.

>

> Gadi Evron.

>

>

[ reply ]
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)
Re: Outbreak warning: possibly Mydoom.C (Now Deadhat/Vesser) Feb 09 2004 07:00PM
Gadi Evron (ge linuxbox org)


 

Privacy Statement
Copyright 2010, SecurityFocus