W32.HLLW.Donk.C

1. Copies itself as:
   
   • %System%\Cool.exe
   • %System%\Wnetlib.exe
     
     
2. Adds the value:
   
   "Microsoft System Checkup"="%System%\Wnetlib.exe"
   
   to the registry keys:
   
   
   • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
   • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices
     
     so that the worm runs when you start Windows.
     
     
3. Adds the value:
   
   "NT Logging Service"= "Syslog32.exe"
   
   to the registry key:
   
   HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
   
   

   ---

   Note: Due to bugs in the code, the worm does not actually drop a file named Syslog32.exe.

   ---

   
   
4. Exploits the DCOM RPC vulnerability, described Microsoft Security Bulletin MS03-026, by sending data to TCP port 135.
   
   
5. Clears the security event log on Windows NT, Windows XP, and Windows 2000.
   
   
6. Listens on TCP port 20.
   
   
7. Attempts to kill processes with the following names:
   
   • WINPPR.EXE
   • CCAPP.EXE
   • RAVMON.EXE
   • NETSTAT.EXE
   • WUPDMGR.EXE
   • QCONSOLE.EXE
   • LUALL.EXE
   • MSBLAST.EXE
     
     
8. Probes administrative shares using the following username and password combinations:
   
   User:
   • Administrator
   • Guest
   • admin
   • Root
     
     Password:
   • admin123
   • login
   • xxx
   • home
   • secret
   • win
   • temp
   • test
   • abc
   • aaa
   • root
   • administrator
   • computer
   • server
   • database
   • 123
   • Admin
   • qwerty
   • password
   • goodman
   • garcia
   • andy
   • cipriani
   • red
   • blue
   • dick
   • xavier
   • kitty
   • scott
   • colin
   • gabriel
   • cruise
   • tom
   • steven
   • pit
   • antonio
   • willson
   • max
   • provolone
   • joe
   • machintosh
   • jack
   • jackie
   • eddy
   • petrovic
   • smith
   • john
   • mikae
   • chris
   • william
   • will
   • fred
   • louie
   • anderson
   • christian
   • leonte
   • aloha
   • mario
   • andrech
   • niteman
   • akim
   • wintzy
   • ortega
   • jesus
   • koniec
   • locke
   • sebah
   • mitza
   • mike
     
     
9. If a connection is made, the worm copies itself to the following folders:
   
   • C:\Winnt\Profiles\All Users\Start Menu\Programs\Startup
   • C:\Windows\Start Menu\Programs\Startup
   • C:\Documents and Settings\All Users\Start Menu\Programs\Startup
   • \Winnt\Profiles\All Users\Start Menu\Programs\Startup
   • \Windows\Start Menu\Programs\Startup
   • \Documents and Settings\All Users\Start Menu\Programs\Startup
     
     and then executes itself.
     
     
10. Downloads files from a hard-coded URL to %Temp%, and then executes them. The possible file names include:
    
    • Navinst.exe
    • Upd32b.exe
    • Upd32a.exe
    • Cool2.exe
      
      

      ---

      Note: %Temp% is a variable. The worm locates the Windows Temp folder and copies itself to that location.

      ---

      
      
11. Connects to a specific IRC server, and then joins a specific channel to accept the instructions from the worm's author. Some of the possible functions are:
    • Flooding a specified host
    • Downloading a file from the worm's author
    • Executing a file

Recommendations

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

• Use a firewall to block all incoming connections from the Internet to services that should not be publicly available. By default, you should deny all incoming connections and only allow services you explicitly want to offer to the outside world.
• 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.
• Ensure that programs and users of the computer use the lowest level of privileges necessary to complete a task. When prompted for a root or UAC password, ensure that the program asking for administration-level access is a legitimate application.
• Disable AutoPlay to prevent the automatic launching of executable files on network and removable drives, and disconnect the drives when not required. If write access is not required, enable read-only mode if the option is available.
• Turn off file sharing if not needed. If file sharing is required, use ACLs and password protection to limit access. Disable anonymous access to shared folders. Grant access only to user accounts with strong passwords to folders that must be shared.
• Turn off and remove unnecessary services. By default, many operating systems install auxiliary services that are not critical. These services are avenues of attack. If they are removed, threats have less avenues of attack.
• If a 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.
• Configure your email server to block or remove email that contains file attachments that are commonly used to spread threats, such as .vbs, .bat, .exe, .pif and .scr files.
• Isolate compromised computers quickly to prevent threats from spreading further. 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.
• If Bluetooth is not required for mobile devices, it should be turned off. If you require its use, ensure that the device's visibility is set to "Hidden" so that it cannot be scanned by other Bluetooth devices. If device pairing must be used, ensure that all devices are set to "Unauthorized", requiring authorization for each connection request. Do not accept applications that are unsigned or sent from unknown sources.
• For further information on the terms used in this document, please refer to the Security Response glossary.