W32.Mydoom.B@mm

W32.Mydoom.B@mm is a mass-mailing worm that arrives as an attachment with the file extension .bat, .cmd, .exe, .pif, .scr, or .zip. When a computer is infected, the worm will set up a backdoor into the system, which can potentially allow an attacker to connect to the computer and use it as a proxy to gain access to its network resources. In addition, the backdoor can download and execute arbitrary files. The worm will perform a Denial of Service (DoS) against www.microsoft.com starting February 3, 2004 and www.sco.com starting February 1, 2004. It also has a trigger date to stop spreading on March 1, 2004. These events will only occur if the worm is run between or after those dates. While the worm will stop spreading on March 1, 2004, the backdoor component will continue to function after this date. Note: Symantec Consumer products that support Worm Blocking functionality automatically detect this threat as it attempts to spread.

Also Known As:	Mydoom.B [F-Secure], W32/Mydoom.b@MM [McAfee], WORM_MYDOOM.B [Trend], Win32.Mydoom.B [Computer Associates], I-Worm.Mydoom.b [Kaspersky], W32/MyDoom-B [Sophos]
Variants:	W32.Mydoom.A@mm, W32.Novarg.A@mm
Type:	Worm
Infection Length:	29,184 bytes, 6,144 bytes
Systems Affected:	Windows 2000, Windows 95, Windows 98, Windows Me, Windows NT, Windows Server 2003, Windows XP
Systems Not Affected:	DOS, Linux, Macintosh, OS/2, UNIX

Virus Definitions (LiveUpdate™ Weekly) January 28, 2004 Virus Definitions (Intelligent Updater) January 28, 2004

Wild Number of infections: 0 - 49 Number of sites: 0 - 2 Geographical distribution: Low Threat containment: Easy Removal: Moderate

Threat Metrics Wild: Low Damage: Medium Distribution: High

Damage

• Payload Trigger: n/a
• Payload: n/a
  • Large scale e-mailing: Sends to email addresses found in a specified set of files.
  • Deletes files: n/a
  • Modifies files: n/a
  • Degrades performance: May perform a Denial of Service against www.microsoft.com and www.sco.com.
  • Causes system instability: n/a
  • Releases confidential info: n/a
  • Compromises security settings: Allows unauthorized remote access.

Distribution

• Subject of email: Varies
• Name of attachment: Varies with an extension of .pif, .scr, .exe, .cmd, .bat, or .zip.
• Size of attachment: 29,184 bytes (varies if it is in .zip format)
• Time stamp of attachment: n/a
• Ports: TCP 80, 1080, 3128, 8080, 10080
• Shared drives: n/a
• Target of infection: n/a

When W32.Mydoom.B@mm is executed, it does the following:

1. Creates the following files:
   
   • %System%\Ctfmon.dll: Ctfmon.dll acts as a proxy server. The backdoor also has the ability to download and execute arbitrary files. It makes use of TCP ports 80, 1080, 3128, 8080, and 10080.
   • %Temp%\Message: This file contains random letters and is displayed using Notepad.
   • %System%\Explorer.exe.
     
     

     ---

     Notes:
   • Explorer.exe is a legitimate file in the Windows 95/98/Me operating systems, but is in the %Windir% folder, not the %System% folder. (By default, this is C:\Windows or C:\Winnt.) Do not delete the legitimate file that is in the %Windir% folder.
   • %System% is a variable: The worm locates the System folder and copies itself to that location. By default, this is C:\Windows\System (Windows 95/98/Me), C:\Winnt\System32 (Windows NT/2000), or C:\Windows\System32 (Windows XP).
   • %Temp% is a variable: The worm locates the temporary folder and copies itself to that location. By default, this is C:\Windows\TEMP (Windows 95/98/Me), or C:\WINNT\Temp (Windows NT/2000), or C:\Document and Settings\<UserName>\Local Settings\Temp (Windows XP).

     ---

     
     
     
2. Terminates the taskmon.exe process if it is running.
   
   
3. Adds the value:
   
   "(Default)" = "%System%\ctfmon.dll"
   
   to the registry key:
   
   HKEY_CLASSES_ROOT\CLSID\{E6FB5E20-DE35-11CF-9C87-00AA005127ED}\InProcServer32
   
   so that Explorer.exe loads Ctfmon.dll.
   
   
4. Adds the value:
   
   "Explorer" = "%System%\Explorer.exe"
   
   to the registry keys:
   
   HKEY_CURRENT_USER\Software\Microsft\Windows\CurrentVersion\Run
   
   HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
   
   so that Explorer.exe is run when you start Windows.
   
   
5. Overwrites the local host file to prevent users from accessing the following sites. This action occurs at each instance the worm runs. If the local system date falls within the date range of the www.microsoft.com DoS, the reference to www.microsoft.com is not written to the hosts file.
   
   • ad.doubleclick.net
   • ad.fastclick.net
   • ads.fastclick.net
   • ar.atwola.com
   • atdmt.com
   • avp.ch
   • avp.com
   • avp.ru
   • awaps.net
   • banner.fastclick.net
   • banners.fastclick.net
   • ca.com
   • click.atdmt.com
   • clicks.atdmt.com
   • dispatch.mcafee.com
   • download.mcafee.com
   • download.microsoft.com
   • downloads.microsoft.com
   • engine.awaps.net
   • fastclick.net
   • f-secure.com
   • ftp.f-secure.com
   • ftp.sophos.com
   • go.microsoft.com
   • liveupdate.symantec.com
   • mast.mcafee.com
   • mcafee.com
   • media.fastclick.net
   • msdn.microsoft.com
   • my-etrust.com
   • nai.com
   • networkassociates.com
   • office.microsoft.com
   • phx.corporate-ir.net
   • secure.nai.com
   • securityresponse.symantec.com
   • service1.symantec.com
   • sophos.com
   • spd.atdmt.com
   • support.microsoft.com
   • symantec.com
   • update.symantec.com
   • updates.symantec.com
   • us.mcafee.com
   • vil.nai.com
   • viruslist.ru
   • windowsupdate.microsoft.com
   • www.avp.ch
   • www.avp.com
   • www.avp.ru
   • www.awaps.net
   • www.ca.com
   • www.fastclick.net
   • www.f-secure.com
   • www.kaspersky.ru
   • www.mcafee.com
   • www.microsoft.com
   • www.my-etrust.com
   • www.nai.com
   • www.networkassociates.com
   • www.sophos.com
   • www.symantec.com
   • www.trendmicro.com
   • www.viruslist.ru
   • www3.ca.com
     
     
6. Attempts to perform a DoS attack against www.microsoft.com and www.sco.com.
   • There is a 70% chance that the worm will perform the DoS against www.microsoft.com if the February 3, 2004 trigger date condition has been met.
   • There is an 80% change that the worm will perform the DoS against www.sco.com if the February 1, 2004 trigger date condition has been met.
     
     The DoS against both sites consists of sending GET requests to the target domain using a direct connection to port 80. The date is taken by using the local system time.
     
     
7. Searches for the email addresses in the files that have the following extensions:
   
   • .htm
   • .sht
   • .php
   • .asp
   • .dbx
   • .tbb
   • .adb
   • .pl
   • .wab
   • .txt
     
     
8. Attempts to send email messages using its own SMTP engine. The worm looks up the mail server that the recipient uses before sending the email. It will prepend the following list of strings to the target domain name. If this is unsuccessful, it will use the local mail server instead.
   
   • gate.
   • ns.
   • relay.
   • mail1.
   • mxs.
   • mx1.
   • smtp.
   • mail.
   • mx.
     
     
9. The email will have the following characteristics:
   
   From: The "From" address may be spoofed.
   
   Subject: The subject will be one of the following:
   Returned mail
   Delivery Error
   Status
   Server Report
   Mail Transaction Failed
   Mail Delivery System
   hello
   hi
   
   Message: The message will be one of the following:
   sendmail daemon reported:
   Error #804 occured during SMTP session. Partial message has been received.
   Mail transaction failed. Partial message is available.
   The message contains Unicode characters and has been sent as a binary attachment.
   The message contains MIME-encoded graphics and has been sent as a binary attachment.
   The message cannot be represented in 7-bit ASCII encoding and has been sent as a binary attachment.
   
   Attachment:
   
   The attachment may have either one or two file extensions. If it does have two, the first extension will be one of the following:
   
   .htm
   .txt
   .doc
   
   The second extension, or the only extension if there is only one, will be one of the following:
   .pif
   .scr
   .exe
   .cmd
   .bat
   .zip (This is an actual .zip file that contains a copy of the worm, sharing the same file name as the .zip. For example, readme.zip can contain readme.exe.)
   
   If the worm has an extension of .exe or .scr, the file will be displayed with the following icon:
   
   
   
   
   
   For all the other file extensions, it will use the icon for that file type.
   
   
10. Copies itself to the Kazaa download folder as one of the following files:
    • icq2004-final
    • Xsharez_scanner
    • BlackIce_Firewall_Enterpriseactivation_crack
    • ZapSetup_40_148
    • MS04-01_hotfix
    • Winamp5
    • AttackXP-1.26
    • NessusScan_pro
      
      with a file extension of one of the following:
      
    • .pif
    • .scr
    • .bat
    • .exe
      
      
11. The worm also contains functionality which allows it to install itself on systems which may have been infected by W32.Novarg.A@mm. This is accomplished as follows:
    • The worm creates two to six threads working in parallel.
    • Each thread scans a randomly picked class-C sized networks, from a.b.c.1 to a.b.c.254, except that it skips networks where a=16, 224, 127 or 128.
    • Between each scanned network, a thread waits 128 ms.
    • Each IP in the scanned class-C is contacted on port 3127, if the connection succeeds, the worm sends an update command along with a copy of itself to be executed on the remote machine.

Symantec Security Response encourages all users and administrators to adhere to the following basic security "best practices":

• Turn off and remove unneeded services. By default, many operating systems install auxiliary services that are not critical, such as an FTP server, telnet, and a Web server. These services are avenues of attack. If they are removed, blended threats have less avenues of attack and you have fewer services to maintain through patch updates.
• If a blended threat exploits one or more network services, disable, or block access to, those services until a patch is applied.
• Always keep your patch levels up-to-date, especially on computers that host public services and are accessible through the firewall, such as HTTP, FTP, mail, and DNS services (for example, all Windows-based computers should have the current Service Pack installed.). Additionally, please apply any security updates that are mentioned in this writeup, in trusted Security Bulletins, or on vendor Web sites.
• Enforce a password policy. Complex passwords make it difficult to crack password files on compromised computers. This helps to prevent or limit damage when a computer is compromised.
• Configure your email server to block or remove email that contains file attachments that are commonly used to spread viruses, such as .vbs, .bat, .exe, .pif and .scr files.
• Isolate infected computers quickly to prevent further compromising your organization. Perform a forensic analysis and restore the computers using trusted media.
• Train employees not to open attachments unless they are expecting them. Also, do not execute software that is downloaded from the Internet unless it has been scanned for viruses. Simply visiting a compromised Web site can cause infection if certain browser vulnerabilities are not patched.

Removal using the Removal Tool
Symantec Security Response has developed a removal tool to clean the infections of variants of W32.Novarg/Mydoom. This is the preferred method in most cases.

Manual Removal
The following instructions pertain to all current and recent Symantec antivirus products, including the Symantec AntiVirus and Norton AntiVirus product lines.

1. Disable System Restore (Windows Me/XP).
2. Remove the entries that were added to the Hosts file.
3. Update the virus definitions.
4. Restart the computer in Safe mode or VGA mode.
5. Run a full system scan and delete all the files detected as W32.Mydoom.B@mm.
6. Delete the values that were added to the registry.
7. Reregister the webcheck.dll file. (This action removes the registry modifications responsible for loading Shimgapi.dll.)
   

• "How to disable or enable Windows Me System Restore"
• "How to turn off or turn on Windows XP System Restore"

• Windows 95/98/Me/NT/2000
  1. Click Start, point to Find or Search, and then click Files or Folders.
  2. Make sure that "Look in" is set to (C:) and that "Include subfolders" is checked.
  3. In the "Named" or "Search for..." box, type:
     
     hosts
     
     
  4. Click Find Now or Search Now.
  5. For each one that you find, right-click the file, and then click "Open With."
  6. Deselect the "Always use this program to open this program" check box.
  7. Scroll through the list of programs and double-click Notepad.
  8. When the file opens, within the file, delete all the entries in the Hosts file where the line begins with 0.0.0.0.
     
     For example:
     
     0.0.0.0     www.microsoft.com
     
     There may be many lines like this. Delete all of them.
     
     
  9. Close Notepad and save your changes when prompted.
     
     
• Windows XP
  1. Click Start, and then click Search.
  2. Click All files and folders.
  3. In the "All or part of the file name" box, type:
     
     hosts
     
     
  4. Verify that "Look in" is set to "Local Hard Drives" or to (C:).
  5. Click "More advanced options."
  6. Check "Search system folders."
  7. Check "Search subfolders."
  8. Click Search.
  9. Click Find Now or Search Now.
  10. For each one that you find, right-click the file, and then click "Open With."
  11. Deselect the "Always use this program to open this program" check box.
  12. Scroll through the list of programs and double-click Notepad.
  13. When the file opens, within the file, delete all the entries in the Hosts file where the line begins with 0.0.0.0.
      
      For example:
      
      0.0.0.0     www.microsoft.com
      
      There may be many lines like this. Delete all of them.
      
      
  14. Close Notepad and save your changes when prompted.
      

• Running LiveUpdate, which is the easiest way to obtain virus definitions: These virus definitions are posted to the LiveUpdate servers once each week (usually on Wednesdays), unless there is a major virus outbreak. To determine whether definitions for this threat are available by LiveUpdate, refer to the Virus Definitions (LiveUpdate).
• Downloading the definitions using the Intelligent Updater: The Intelligent Updater virus definitions are posted on U.S. business days (Monday through Friday). You should download the definitions from the Symantec Security Response Web site and manually install them. To determine whether definitions for this threat are available by the Intelligent Updater, refer to the Virus Definitions (Intelligent Updater).
  
  The Intelligent Updater virus definitions are available: Read "How to update virus definition files using the Intelligent Updater" for detailed instructions.

• For Windows 95, 98, Me, 2000, or XP users, restart the computer in Safe mode. For instructions, read the document, "How to start the computer in Safe Mode."
• For Windows NT 4 users, restart the computer in VGA mode.

1. Start your Symantec antivirus program and make sure that it is configured to scan all the files.
   • For Norton AntiVirus consumer products: Read the document, "How to configure Norton AntiVirus to scan all files."
   • For Symantec AntiVirus Enterprise products: Read the document, "How to verify that a Symantec Corporate antivirus product is set to scan all files."
2. Run a full system scan.
3. If any files are detected as infected with W32.Mydoom.B@mm, click Delete.

1. Click Start, and then click Run. (The Run dialog box appears.)
   
2. Type regedit
   
   Then click OK. (The Registry Editor opens.)
   
   
3. Navigate to each of these keys:
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
   
   HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
   
   
4. In the right pane, delete the value:
   
   "Explorer"="%System%\explorer.exe"
   
   

   ---

   Note: %System% is a variable that refers to the location of the System folder. By default, this is C:\Windows\System (Windows 95/98/Me), C:\Winnt\System32 (Windows NT/2000), or C:\Windows\System32 (Windows XP).

   ---

   
   
5. Exit the Registry Editor.

1. Click Start, and then click Run. (The Run dialog box appears.)
2. Type, or copy and paste, the following text:
   
   regsvr32 webcheck.dll
   
   
3. Click OK. When you see the message, "DllRegisterServer in webcheck.dll
   succeeded," click OK.

Additional information:

When W32.Mydoom.B@mm sends email, it avoids distributing to the domains that contain any of the following strings:

• avp
• syma
• icrosof
• msn.
• hotmail
• panda
• sopho
• borlan
• inpris
• example
• mydomai
• nodomai
• ruslis
• .gov
• gov.
• .mil
• foo.
• berkeley
• unix
• math
• bsd
• mit.e
• gnu
• fsf.
• ibm.com
• google
• kernel
• linux
• fido
• usenet
• iana
• ietf
• rfc-ed
• sendmail
• arin.
• ripe.
• isi.e
• isc.o
• secur
• acketst
• pgp
• tanford.e
• utgers.ed
• mozilla
  
  
  accounts that match any of the following strings:

• root
• info
• samples
• postmaster
• webmaster
• noone
• nobody
• nothing
• anyone
• someone
• your
• you
• me
• bugs
• rating
• site
• contact
• soft
• no
• somebody
• privacy
• service
• help
• not
• submit
• feste
• ca
• gold-certs
• the.bat
• page
  
  
  or accounts that contain any of the following strings:

• admin
• icrosoft
• support
• ntivi
• unix
• bsd
• linux
• listserv
• certific
• google
• accoun

• adam
• alex
• alice
• andrew
• anna
• bill
• bob
• brenda
• brent
• brian
• claudia
• dan
• dave
• david
• debby
• fred
• george
• helen
• jack
• james
• jane
• jerry
• jim
• jimmy
• joe
• john
• jose
• julie
• kevin
• leo
• linda
• maria
• mary
• matt
• michael
• mike
• peter
• ray
• robert
• sam
• sandra
• serg
• smith
• stan
• steve
• ted
• tom

Revision History:

• February 4, 2004: Updated Removal Instructions.
• January 30, 2004: Updated with link to removal tool for W32.Mydoom
• January 29, 2004: Updated information pertaining to modification of hosts file.
• January 28, 2004: Updated information pertaining to DoS payload. Provided link to beta definitions.
• January 30, 2003. Changed manual removal to use regsvr32 command to reregister the webcheck.dll file rather than do this in the registry.

Write-up by: Scott Gettis