Symantec United States
global sites
products
purchase
service and support
security updates
downloads
about symantec
search
feedback


©1995-2009 Symantec Corporation.
All rights reserved.

Legal Notices
Privacy Policy

security updates

W32.Spybot.ANDM

Category 2
Discovered on: January 03, 2007
Last Updated on: February 01, 2007 06:46:34 AM



W32.Spybot.ANDM is a worm that spreads through mIRC and to network shares protected by weak passwords. It also spreads by exploiting system vulnerabilities.

Notes:
  • Virus definitions dated prior to January 3rd, 2007 rev. 53 may detect this as W32.Spybot.Worm
  • Recent variants of the Spybot worm family exploit several known vulnerabilities, including a SAV 10/SCS 3 vulnerability (SYM06-010), reported in May 2006. A patch for this vulnerability was made available at that time. Symantec highly recommends that users of the affected products patch their systems as soon as they are able to help avoid the spread of this particular Sybot worm family. If systems are infected with any Spybot variant and this security patch has not been applied please read the document, Attempting to migrate from 10.x to a newer version fails after becoming infected with a worm which exploits SYM06-010.
  • IPS signatures against all known and unknown exploits of SYM06-010 were released on May 26, 2006.
  • Excessive network traffic caused by an infection may result in a significant degradation of network performance.
 

Type: Worm
Infection Length: 168,960 bytes
Systems Affected: Windows 2000, Windows 95, Windows 98, Windows Me, Windows NT, Windows Server 2003, Windows XP

protection
  • Virus Definitions (LiveUpdate™ Plus)
  • January 03, 2007

  • Virus Definitions (LiveUpdate™ Daily)
  • January 03, 2007

  • Virus Definitions (LiveUpdate™ Weekly)
  • January 03, 2007

  • Virus Definitions (Intelligent Updater)
  • January 03, 2007

    threat assessment

    Wild

    Threat Metrics

    Medium Medium Medium

    Wild:
    Medium

    Damage:
    Medium

    Distribution:
    Medium

    Damage

    Distribution

    technical details

    When W32.Spybot.ANDM is executed, it performs the following actions:

    1. Copies itself as any of the following files:

      • %System%\wnuserv.exe
      • %System%\ctfmom.exe
      • %System%\napi32.exe
      • %System%\soundman.exe

        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).

    2. Creates a temporary batch file named c:\a.bat, which in turn creates a registry file in the temporary folder named 1.reg.

    3. Adds the values:

      "Windows System Service" = "wnuserv.exe"
      "Windows System Service" = "wnuserv.exe"
      "Windows Update Firewall System" = "ctfmom.exe"
      "Windows Update Firewall System" = "ctfmom.exe"
      "Windows Logon Service" = "napi32.exe"
      "Windows Logon Service" = "napi32.exe"
      "Microsoft Sounds" = "soundman.exe"
      "Microsoft Sounds" = "soundman.exe"


      to the registry subkey:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunServices

      so that it runs every time Windows starts.

    4. Adds the value:

      "Windows System Service" = "wnuserv.exe"

      to the registry subkey:

      HKEY_CURRENT_USER\Software\Microsoft\OLE\Windows

    5. Modifies the value:

      "TransportBindName" = ""

      in the registry subkey:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters

    6. Modifies the value:

      "Start" = "4"

      in the registry subkeys:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wuauserv
      HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\wscsvc


    7. Modifies the values:

      "EnableDCOM" = "N"
      "EnableRemoteConnect" = "N"


      in the registry subkey:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole

    8. Modifies the value:

      "restrictanonymous" = "1"

      in the registry subkey:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

      to prevent NULL session enumeration of the host.

    9. Modifies the value:

      "Enabled" = "0"

      in the registry subkey:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\PCT1.0\Server

    10. Modifies the values:

      "AutoShareWks" = "0"
      "AutoShareServer" = "0"

      in the registry subkey:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters

    11. Modifies the values:

      "NameServer" = ""
      "ForwardBroadcasts" = "0"
      "IPEnableRouter" = "0"
      "Domain" = ""
      "SearchList" = ""
      "UseDomainNameDevolution" = "1"
      "EnableICMPRedirect" = "0"
      "DeadGWDetectDefault" = "1"
      "DontAddDefaultGatewayDefault" = "0"
      "EnableSecurityFilters" = "1"
      "AllowUnqualifiedQuery" = "0"
      "PrioritizeRecordData" = "1"
      "TCP1320Opts" = "3"
      "KeepAliveTime" = "23280"
      "BcastQueryTimeout" = "002ee"
      "BcastNameQueryCount" = "1"
      "CacheTimeout" = "0ea60"
      "Size/Small/Medium/Large" = "3"
      "LargeBufferSize" = "01000"
      "SynAckProtect" = "2"
      "PerformRouterDiscovery" = "0"
      "EnablePMTUBHDetect" = "0"
      "FastSendDatagramThreshold " = "400"
      "StandardAddressLength " = "18"
      "DefaultReceiveWindow " = "4000"
      "DefaultSendWindow" = "4000"
      "BufferMultiplier" = "200"
      "PriorityBoost" = "2"
      "IrpStackSize" = "4"
      "IgnorePushBitOnReceives" = "0"
      "DisableAddressSharing" = "0"
      "AllowUserRawAccess" = "0"
      "DisableRawSecurity" = "0"
      "DynamicBacklogGrowthDelta" = "32"
      "FastCopyReceiveThreshold" = "400"
      "LargeBufferListDepth" = "a"
      "MaxActiveTransmitFileCount" = "2"
      "MaxFastTransmit" = "40"
      "OverheadChargeGranularity" = "1"
      "SmallBufferListDepth" = "20"
      "SmallerBufferSize" = "80"
      "TransmitWorker" = "20"
      "DNSQueryTimeouts" = "31,00,00,00,32,00,00,00,32,00,00,00,34,00,00,00,38,00,00,00,30,00,00,00,00,00"
      "DefaultRegistrationTTL" = "14"
      "DisableReplaceAddressesInConflicts" = "0"
      "DisableReverseAddressRegistrations" = "1"
      "UpdateSecurityLevel " = "0"
      "DisjointNameSpace" = "1"
      "QueryIpMatching" = "0"
      "NoNameReleaseOnDemand" = "1"
      "EnableDeadGWDetect" = "0"
      "EnableFastRouteLookup" = "1"
      "MaxFreeTcbs" = "7d0"
      "MaxHashTableSize" = "800"
      "SackOpts" = "1"
      "Tcp1323Opts" = "3
      "TcpMaxDupAcks" = "1"
      "TcpRecvSegmentSize" = "585"
      "TcpSendSegmentSize" = "585"
      "TcpWindowSize" = "7d200"
      "DefaultTTL" = "30"
      "TcpMaxHalfOpen" = "4b"
      "TcpMaxHalfOpenRetried" = "50"
      "TcpTimedWaitDelay" = "0"
      "MaxNormLookupMemory" = "30d40"
      "FFPControlFlags" = "1"
      "FFPFastForwardingCacheSize" = "30d40"
      "MaxForwardBufferMemory" = "19df7"
      "MaxFreeTWTcbs" = "7d0"
      "GlobalMaxTcpWindowSize" = "7d200"
      "EnablePMTUDiscovery" = "1"
      "ForwardBufferMemory" = "19df7"

      in the registry subkey:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

    12. Modifies the values:

      "MaxConnectionsPer1_0Server" = "50"
      "MaxConnectionsPerServer" = "50"

      in the registry subkey:

      HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings


    13. Starts to log keystrokes whenever the user attempts to access sites that contain the following strings:

      • e-gold
      • PayPal
      • StormPay
      • Vodafone
      • Poste Italiane
      • eBay
      • Yahoo!
      • Banca Sella
      • Email
      • Bank of America
      • exploit
      • Benvenuto a gmail
      • Msn
      • pagamento paga

    14. Opens a back door and connects to an IRC server at any of the following hosts:

      • baba.bestunix.org
      • server.cisco-systems.jp
      • pepe83.rr.nu
      • pepe84.rr.nu
      • pepe85.rr.nu

    15. The attacker may perform the following actions on the compromised computer:

      • Copy or delete files
      • Upload and download files
      • Steal CD keys from various games
      • Log keystrokes and capture webcam
      • Show status
      • Show IP address
      • Portscan the network for vulnerable computers
      • Scan vulnerabilities
      • Start ftp and tftp
      • Start Internet Explorer
      • End processes
      • Stop other worms
      • Stop security-related services
      • List processes
      • Use a network sniffer

    16. Spreads by exploiting the following vulnerabilities:

    17. Attempts to spread through mIRC and to network shares protected by weak passwords.

    This worm attempts to exploit a previously addressed vulnerability in Symantec Client Security and Symantec Antivirus, SYM06-010; patches for the particular Symantec product vulnerability have been available since Thursday, May 25th, 2006. As a result, customers who have applied the patch in their environment are unaffected by the worm's attempt to leverage the Symantec vulnerability for an attack. Customers running Symantec Client Security or Symantec intrusion prevention (IPS) capable products are protected against all known and unknown exploits of SYM06-010 via IPS signatures released on May 26th, 2006.

    recommendations

    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 instructions

    Removal using the W32.Spybot.ANDM Removal Tool
    Symantec Security Response has developed a removal tool to clean the infections of W32.Spybot.ANDM. Use this removal tool first, as it is the easiest way to remove this threat.

    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. Update the virus definitions.
    3. Run a full system scan.
    4. Delete any values added to the registry.
    5. Restore the default TCP/IP settings.
    For specific details on each of these steps, read the following instructions.

    1. To disable System Restore (Windows Me/XP)
    If you are running Windows Me or Windows XP, we recommend that you temporarily turn off System Restore. Windows Me/XP uses this feature, which is enabled by default, to restore the files on your computer in case they become damaged. If a virus, worm, or Trojan infects a computer, System Restore may back up the virus, worm, or Trojan on the computer.

    Windows prevents outside programs, including antivirus programs, from modifying System Restore. Therefore, antivirus programs or tools cannot remove threats in the System Restore folder. As a result, System Restore has the potential of restoring an infected file on your computer, even after you have cleaned the infected files from all the other locations.

    Also, a virus scan may detect a threat in the System Restore folder even though you have removed the threat.

    For instructions on how to turn off System Restore, read your Windows documentation, or one of the following articles:
    Note:
    When you are completely finished with the removal procedure and are satisfied that the threat has been removed, reenable System Restore by following the instructions in the aforementioned documents.

    For additional information, and an alternative to disabling Windows Me System Restore, see the Microsoft Knowledge Base article: Antivirus Tools Cannot Clean Infected Files in the _Restore Folder (Article ID: Q263455).

    2. To update the virus definitions
    Symantec Security Response fully tests all the virus definitions for quality assurance before they are posted to our servers. There are two ways to obtain the most recent virus definitions:
    • Running LiveUpdate, which is the easiest way to obtain virus definitions:
      • If you use Norton AntiVirus 2006, Symantec AntiVirus Corporate Edition 10.0, or newer products, LiveUpdate definitions are updated daily. These products include newer technology.
      • If you use Norton AntiVirus 2005, Symantec AntiVirus Corporate Edition 9.0, or earlier products, LiveUpdate definitions are updated weekly. The exception is major outbreaks, when definitions are updated more often.
    • Downloading the definitions using the Intelligent Updater: The Intelligent Updater virus definitions are posted daily. 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 Virus Definitions (Intelligent Updater).

      The latest Intelligent Updater virus definitions can be obtained here: Intelligent Updater virus definitions. For detailed instructions read the document: How to update virus definition files using the Intelligent Updater.

    3. To run a full system scan
    1. Start your Symantec antivirus program and make sure that it is configured to scan all the files.
    2. Run a full system scan.
    3. If any files are detected, follow the instructions displayed by your antivirus program.

    Important: If you are unable to start your Symantec antivirus product or the product reports that it cannot delete a detected file, you may need to stop the risk from running in order to remove it. To do this, run the scan in Safe mode. For instructions, read the document, How to start the computer in Safe Mode. Once you have restarted in Safe mode, run the scan again.

    After the files are deleted, restart the computer in Normal mode and proceed with the next section.

    Warning messages may be displayed when the computer is restarted, since the threat may not be fully removed at this point. You can ignore these messages and click OK. These messages will not appear when the computer is restarted after the removal instructions have been fully completed. The messages displayed may be similar to the following:

    Title: [FILE PATH]
    Message body: Windows cannot find [FILE NAME]. Make sure you typed the name correctly, and then try again. To search for a file, click the Start button, and then click Search.


    4. To delete the value from the registry
    Important: Symantec strongly recommends that you back up the registry before making any changes to it. Incorrect changes to the registry can result in permanent data loss or corrupted files. Modify the specified subkeys only. For instructions refer to the document: How to make a backup of the Windows registry.
    1. Click Start > Run.
    2. Type regedit
    3. Click OK.

      Note: If the registry editor fails to open the threat may have modified the registry to prevent access to the registry editor. Security Response has developed a tool to resolve this problem. Download and run this tool, and then continue with the removal.

    4. Navigate to the subkey:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunServices

    5. In the right pane, delete the value:

      "Windows System Service" = "wnuserv.exe"
      "Windows System Service" = "wnuserv.exe"
      "Windows Update Firewall System" = "ctfmom.exe"
      "Windows Update Firewall System" = "ctfmom.exe"
      "Windows Logon Service" = "napi32.exe"
      "Windows Logon Service" = "napi32.exe"
      "Microsoft Sounds" = "soundman.exe"
      "Microsoft Sounds" = "soundman.exe"

    6. Navigate to the subkey:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters

    7. In the right pane, reset the value to the default value:

      "TransportBindName" = "\Device\"

    8. Navigate to the subkeys:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wuauserv
      HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\wscsvc

    9. In the right pane, reset the value to the default value:

      "Start" = "4"

    10. Navigate to the subkey:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole

    11. In the right pane, reset the values to the default values:

      "EnableDCOM" = "N"
      "EnableRemoteConnect" = "N"


    12. Navigate to the subkey:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

    13. In the right pane, reset the value to the default value:

      "restrictanonymous" = "1"

    14. Navigate to the subkey:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\PCT1.0\Server

    15. In the right pane, reset the value to the default value:

      "Enabled" = "0"

    16. Navigate to the subkey:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters

    17. In the right pane, reset the values to the default values:

      "AutoShareWks" = "0"
      "AutoShareServer" = "0"


    18. Navigate to the subkey:

      HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings

    19. In the right pane, reset the values to the default values:

      "MaxConnectionsPer1_0Server" = "50"
      "MaxConnectionsPerServer" = "50"

    20. Navigate to the subkey:

      HKEY_CURRENT_USER\Software\Microsoft\OLE\Windows


    21. In the right pane, delete the value:

      "Windows System Service" = "wnuserv.exe"

    22. Exit the Registry Editor.


    5. To restore the default TCP/IP settings
    This threat makes changes to the compromised computer's TCP/IP settings. In order to restore the default TCP/IP settings, read the document: How to reset Internet Protocol (TCP/IP) in Windows XP.

    Revision History:

    January 12, 2006: Added information regarding Symantec vulnerability patch.


    Write-up by: Jeong Mun