W32.Spybot.NLX

1. Copies itself as %Windir%\iTunesMusic.exe.
   
   Note: %Windir% is a variable that refers to the Windows installation folder. By default, this is C:\Windows or C:\Winnt.
   
   
2. Drops the file %System%\rdriv.sys, which is detected as Trojan.Cachecachekit. This file operates as a rootkit hiding the presence of the iTunesMusic.exe file and service.
   
   
3. Creates the following registry subkeys to register itself as a service:
   
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rdriv
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iTunesMusic 
   
   Note: %System% is a variable that refers to 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).
   
   The service has the following properties:
   
   Display Name: iTunesMusic
   Path to Executable: %Windir%\iTunesMusic.exe
   Description: W32.Spybot.NLX is executed at startup.
   
   
4. Sets the value:
   
   "restrictanonymous" = "1"
   
   in the subkey:
   
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
   
   to modify access to network shares.
   
   
   
5. Sets the value:
   
   "EnableDCOM" = "N"
   
   in the subkey:
   
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole
   
   to disable DCOM.
   
   
   
   
6. Creates the following registry subkeys:
   
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\
   Legacy_ITUNESMUSIC\0000
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\
   Legacy_RDRIV\0000
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanger\
   parameters\AutoShareServer
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanger\
   parameters\AutoShareWks
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
   Lanmanworkstation\parameters\AutoShareServer
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
   Lanmanworkstation\parameters\AutoShareWks
   
   
7. Modifies several registry subkeys to lower the Internet Explorer Security Zones settings.
   
   
8. Attempts to disable the Windows XP Service Pack 2 Security Center and the Windows firewall by altering multiple registry subkeys.
   
   
9. Adds the value:
   
   "DoNotAllowXPSP2" = "1"
   
   to the registry subkey:
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
   
   to prevent the installation of Windows XP Service Pack 2 on the compromised computer.
   
   
10. Adds the value:
    
    "AUOptions" = "1"
    
    to the registry subkey:
    
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CurrentVersion\WindowsUpdate
    
    to prevent the installation of Windows XP Service Pack 2 on the compromised computer.
    
    
11. Attempts to open a back door by connecting to the IRC channel on 69.31.76.179, through TCP port 4367.
    
    
12. Listens for commands that allow the attacker to perform any of the following actions:
    
    
    • Download and execute files
    • List, stop, and start processes and threads
    • Launch ACK, SYN, UDP, and ICMP denial of service attacks
    • Perform port redirection
    • Send files over IRC
    • Send email using its own SMTP engine
    • Start a local HTTP, FTP, or TFTP server
    • Search for files on the compromised computer
    • Log keystrokes
    • Access network shares and copy itself to those network shares
    • Scan the network for vulnerable computers by means of port scanning
    • Capture screenshots, data from the clipboard, and footage from webcams
    • Visit URLs
    • Flush the DNS and ARP caches
    • Open a command shell on the compromised computer
    • Start a SOCKS4 proxy server
    • Add and delete network shares and disable DCOM
    • Reboot the compromised computer
    • Intercept packets on the local area network
    • Retrieve the currently logged on user's Windows password from memory
    • Send net send messages
    • Delete registry loading points from other programs and malware
      
      
13. Scans for computers vulnerable to one or more of the following exploits:
    
    
    • The Microsoft Windows DCOM RPC Interface Buffer Overrun Vulnerability (described in Microsoft Security Bulletin MS03-026).
    • The Microsoft Windows Local Security Authority Service Remote Buffer Overflow (as described in Microsoft Security Bulletin MS04-011).
    • The Microsoft Windows SSL Library Denial of Service Vulnerability (described in Microsoft Security Bulletin MS04-011).
    • The Vulnerabilities in the Microsoft SQL Server 2000 or MSDE 2000 audit (as described in Microsoft Security Bulletin MS02-061) using UDP port 1434.
    • The UPnP NOTIFY Buffer Overflow vulnerability (as described in Microsoft Security Bulletin MS01-059).
    • The Workstation Service Buffer Overrun vulnerability (as described in Microsoft Security Bulletin MS03-049) using TCP port 445. Windows XP users are protected against this vulnerability if Microsoft Security Bulletin MS03-043 has been applied. Windows 2000 users must apply MS03-049.
    • The DameWare Mini Remote Control Server Pre-Authentication Buffer Overflow vulnerability (described in CAN-2003-0960.)
      
      
14. Attempts to propagate through back doors opened by variants of the Beagle, Sasser, and Mydoom worms, and by variants of Backdoor.NetDevil, Backdoor.Subseven, Backdoor.Kuang, and Backdoor.Optix.
    
    
15. Attempts to steal the CD keys associated with a number of computer games.
    
    
16. Attempts to spread to randomly generated IP addresses by copying itself to network shares. The worm attempts to use the following list of passwords to access the network shares:
    
    
    • 007
    • 123
    • 1234
    • 12345
    • 123456
    • 1234567
    • 12345678
    • 123456789
    • 1234567890
    • 2000
    • 2001
    • 2002
    • 2003
    • 2004
    • access
    • accounting
    • accounts
    • adm
    • administrador
    • administrat
    • administrateur
    • administrator
    • admins
    • asd
    • backup
    • bill
    • bitch
    • blank
    • bob
    • brian
    • changeme
    • chris
    • cisco
    • compaq
    • computer
    • control
    • data
    • database
    • databasepass
    • databasepassword
    • db1
    • db1234
    • db2
    • dba
    • dbpass
    • dbpassword
    • default
    • dell
    • demo
    • domain
    • domainpass
    • domainpassword
    • eric
    • exchange
    • fred
    • fuck
    • george
    • god
    • guest
    • hell
    • hello
    • home
    • homeuser
    • ian
    • ibm
    • internet
    • intranet
    • jen
    • joe
    • john
    • kate
    • katie
    • lan
    • lee
    • linux
    • loginpass
    • luke
    • mail
    • main
    • mary
    • mike
    • neil
    • nokia
    • none
    • null
    • oem
    • oeminstall
    • oemuser
    • office
    • oracle
    • orainstall
    • outlook
    • owner
    • pass
    • pass1234
    • passwd
    • password
    • password1
    • peter
    • pwd
    • qaz
    • qwe
    • qwerty
    • sam
    • server
    • sex
    • siemens
    • slut
    • sql
    • sqlpassoainstall
    • staff
    • student
    • sue
    • susan
    • teacher
    • technical
    • test
    • unix
    • web
    • win2000
    • win2k
    • win98
    • windows
    • winnt
    • winpass
    • winxp
    • www
    • wwwadmin
    • zxc

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.