Discovered: February 25, 2005
Updated: February 13, 2007 12:34:12 PM
Systems Affected: Windows
W32.Spybot.KEG is a worm that has distributed denial of service and back door capabilities. The worm spreads to network shares protected by weak passwords and by exploiting vulnerabilities.
Antivirus Protection Dates
- Initial Rapid Release version February 25, 2005
- Latest Rapid Release version May 07, 2019 revision 006
- Initial Daily Certified version February 25, 2005
- Latest Daily Certified version May 07, 2019 revision 008
- Initial Weekly Certified release date February 27, 2005
Click here for a more detailed description of Rapid Release and Daily Certified virus definitions.
When W32.Spybot.KEG is executed, it performs the following actions:
- Creates the following copy of itself:
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).
- Adds the value:
to the registry subkey:
so that the W32.Spybot.KEG runs every time Windows starts.
- Attempts to open a back door by connecting to the IRC channel through one of the following:
- #final on the omg.pj34r.us
- ed.teh-fbi.us domain, through TCP port 9832.
- Listens for commands that allow the attacker to perform 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 hosts by means of port scanning.
- Captures screenshots, data from the clipboard, and footage from webcams.
- Visit URLs.
- Flush the DNS and ARP caches.
- Open a command shell on the infected 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.
- May scan for computers vulnerable to one or more of the following exploits:
- The DCOM RPC Vulnerability (described in Microsoft Security Bulletin MS03-026), using TCP port 135, (BID 8205).
- The Microsoft Windows Local Security Authority Service Remote Buffer Overflow (described in Microsoft Security Bulletin MS04-011).
- The Workstation Service Buffer Overrun Vulnerability (described in Microsoft Security Bulletin MS03-049), using TCP port 445. Windows XP users are protected against this vulnerability if the patch in Microsoft Security Bulletin MS03-043 has been applied. Windows 2000 users must apply the patch in Microsoft Security Bulletin MS03-049.
- Microsoft Windows SSL Library Denial of Service Vulnerability (described in Microsoft Security Bulletin MS04-011).
- The Microsoft SQL Server User Authentication Remote Buffer Overflow Vulnerability (described in Microsoft Security Bulletin MS02-056).
- The UPnP NOTIFY Buffer Overflow Vulnerability (described in Microsoft Security Bulletin MS01-059).
- The DameWare Mini Remote Control Server Pre-Authentication Buffer Overflow vulnerability (described in CAN-2003-0960).
- Attempts to propagate through back doors opened by one of the following variants:
- Mydoom worms
- Attempts to steal the CD keys associated with a number of computer games.
- 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:
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.
The following instructions pertain to all current and recent Symantec antivirus products, including the Symantec AntiVirus and Norton AntiVirus product lines.
- Disable System Restore (Windows Me/XP).
- Update the virus definitions.
- Run a full system scan and delete all the files detected as W32.Spybot.KEG.
- Delete the value that was added to the registry.
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:
- "How to disable or enable Windows Me System Restore"
- "How to turn off or turn on Windows XP System Restore"
Note: When you are completely finished with the removal procedure and are satisfied that the threat has been removed, re-enable 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: 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 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 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.
3. To scan for and delete the infected files
- 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."
- Run a full system scan.
- If any files are detected as infected withW32.Spybot.KEG, click Delete.
Note: If your Symantec antivirus product reports that it cannot delete an infected file, Windows may be using the file. To fix 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 section 4.
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. Read the document, "How to make a backup of the Windows registry ," for instructions.
- Click Start > Run.
- Type regedit
Then click OK.
- Navigate to the subkey:
- In the right pane, delete the value:
- Exit the Registry Editor.
Writeup By: Candid Wueest