bugtraq - Re: Outbreak warning: possibly Mydoom.C (Now Deadhat/Vesser)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <40289477.23172.1F1A9070@localhost>
Date: Tue, 10 Feb 2004 08:21:11 +1300
From: Nick FitzGerald <nick@...us-l.demon.co.uk>
To: bugtraq@...urityfocus.com
Subject: Re: Outbreak warning: possibly Mydoom.C (Now Deadhat/Vesser)

K-OTiK Security <Special-Alerts@...tik.com> wrote:

> it's not mydoom.c - ...

Correct.

> ... his name is Vesser (W32.HLLW.Deadhat) :

Not.

Vesser (which a few AV companies have called Deadhat) was discovered 
early in the weekend spreading via Mydoom.A-infected machiens (and 
rpesumably it would also hit the occasional Mydoom,.B out there too).  
What Gadi alerted on as Mydoom.C has been agreed following analysis by 
AV industry experts to be sufficiently different in critical ways from 
Mydoom to be put in a new family and will be called Doomjuice.A by most 
AVs.

> 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

Correct, but irrelevant to this thread...

-- 
Nick FitzGerald
Computer Virus Consulting Ltd.
Ph/FAX: +64 3 3529854