MyDoom.K worm variant appeared on May 21st, 2004. It is functionally similar to MyDoom.E variant, but does not spread to Kazaa file sharing network and does not perform a DoS (Denial of Service) attack. The worm drops a backdoor component that listens on port 3127.
Once detected, the F-Secure security product will automatically disinfect the suspect file by either deleting it or renaming it.
More scanning & removal options
More information on scanning or removal options is available in the documentation for your F-Secure security product on the Downloads section of our Home - Global site.
You may also refer to the Knowledge Base on the F-Secure Community site for further assistance.
Eliminating a Local Network Outbreak
If the infection is in a local network, please follow the instructions on this webpage:
MyDoom.K worm's file is a PE executable 50176 bytes long compressed with a modified UPX file compressor. The backdoor DLL is a 4608 bytes long, also compressed with a modified UPX file compressor.
Installation to system
When the worm's file is run, it creates a separate thread that generates garbage data file and then opens it with Notepad. Then this thread terminates.
After that the worm drops SHIMGAPI.DLL file into Windows System folder. This file is a backdoor (hacker's remote access) component. It is started as a thread of Explorer from the following Registry key:
Finally the worm installs itself to system. It copies itself as RUNDLL6.EXE file to Windows System directory and creates a startup key for this file in the Registry:
- [HKLM\Software\Microsoft\Windows\CurrentVersion\Run] "rundll" = "%winsysdir%\rundll6.exe"
where %winsysdir% represents Windows System directory name.
Additionally the worm deletes the following Registry keys:
- [HKLM\Software\Microsoft\Windows\CurrentVersion\Run] "SVHOST" "TaskMon"
Spreading in e-mails
The worm spreads itself in e-mail messages. To locate e-mail addresses to spread to, the worm reads Address Book file name from the Registry:
- [HKCU\Software\Microsoft\WAB\WAB4\Wab File Name]
Then it browses through the Address Book file and collects e-mail addresses from there. Additionally the worm looks for e-mail addresses in files with the following extensions:
The worm avoids using e-mail addresses that contain the following substrings:
The worm can fake the sender's e-mail address. It composes e-mail addresses from 2 parts: user name and domain name. Here is the list of user names that the worm uses:
Here is the list of domain names that the worm uses:
The subject for the infected message is selected from the following variants:
- Mail Delivery System
- Mail Transaction Failed
- Server Report
The body of the infected message can contain one of the following:
- The message cannot be represented in 7-bit ASCII encoding and has been sent as a binary attachment.
- The message contains Unicode characters and has been sent as a binary attachment.
- Mail transaction failed. Partial message is available.
The attachment name can be one of the following:
The attachment can have 2 extensions. In such case the first extension can be:
And the second or the only extension can be:
The worm can also send itseld inside a ZIP archive.
The worm drops a backdoor component that starts as a thread of Explorer and listens to port 3127 for commands from remote hackers.
Additionally the worm tries to connect to 'sipper112.netfirms.com' website. At the moment of creation of this description the site was not accessible because it exceeded its its daily bandwidth limit.