1. Symantec/
  2. Security Response/
  3. W32.IRCBot.NG


Risk Level 2: Low

April 7, 2011
April 7, 2011 11:09:27 AM
Infection Length:
175,000 bytes
Systems Affected:
CVE References:
CVE-2008-4250, CVE-2010-2568
When the worm is executed, it creates the following file:
%UserProfile%\Application Data\[RANDOM CHARACTERS].exe

It then creates the following registry entry, so that it starts when Windows starts:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\"[RANDOM CHARACTERS]" = "%UserProfile%\Application Data\[RANDOM CHARACTERS].exe"

It then injects itself into the explorer.exe and winlogon.exe processes.

The worm also contains rootkit capabilities, which hide its file and registry entries.

The worm then opens a back door and connects to a predetermined IRC server, allowing an attacker to perform any of the following actions:
  • Scan Internet Explorer and Firefox traffic for user names and passwords.
  • Intercept FTP traffic and extract user name and passwords.
  • Intercept traffic from instant messaging clients.
  • Intercept and block specific IRC messages.
  • Block downloads of .exe, .com, .pif, and .scr files.
  • Modify responses to DNS requests, redirecting domains to specific IPs or blocking them entirely.
  • Insert links into MSN Messenger messages in order to download copies of the worm.
  • Copy itself to removable drives and create autorun.inf files to spread.

It then spreads through removable drives, MSN Messenger, and by exploiting the following vulnerabilities:


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.
Writeup By: Gavin O'Gorman
Summary| Technical Details| Removal

Search Threats

Search by name
Example: W32.Beagle.AG@mm
STAR Antimalware Protection Technologies
2016 Internet Security Threat Report, Volume 21
  • Twitter
  • Facebook
  • LinkedIn
  • Google+
  • YouTube