Variants are unavailable.
W32/Rustock is a backdoor trojan that belongs to a family of rootkit-enabled trojans that were primarily developed to use infected systems as covert proxies to send spam e-mails.
W32/Rustock consists of three components.† The first component is a dropper, the second is a driver installer and the third is the actual rootkit driver.† All of the components are encrypted and the driver component is compressed with aPLib. The dropper component creates the rootkit installer to appear as a legitimate service.† The rootkit installer decrypts and decompresses the actual rootkit driver code, injects the code into itself, and transfers the execution to the rootkit driver code.† The rootkit driver then hooks the system functions, ntoskrnl.exe and ntdll.exe. The trojan uses multiple encryption and decryption techniques along with polymorphic behavior to avoid detection.†
Virus definitions are available.
W32/Rustock is a trojan that installs a rootkit on the infected system that allows an unauthenticated remote attacker to execute commands.† The infected systems are generally used for sending spam e-mails.
W32/Rustock creates the following files on an infected system:
When the dropper component of Win32/Rustock is executed, it examines global events to determine if the rootkit is already running.
The dropper creates the rootkit driver installer and its updates. The installer component is decrypted and installed as a system driver. The dropper component may attempt to create the driver installer component as a legitimate and rarely used system driver such as beep or null. If the driver installer component cannot successfully use beep or null, it may randomly generate a name or use one of the following names:
During the infection routine a registry entry is made to indicate the presence of rootkit driver installer. A rootkit driver that uses the name 7005d59.sys, creates the following registry entry on infected systems:
ImagePath = \SystemRoot\System32\drivers\7005d59.sys
Type = 1
Start = 1
ErrorControl = 1
The driver installer decrypts and then decompresses the rootkit driver code, injects the copy of the driver into itself and transfers the execution to the code of the rootkit driver. The rootkit driver uses a hook to interface with system functions to increase detection complexity. The driver updates System Service Dispatch Table (SSDT), which allows the driver to filter requests containing the driver name and help avoid detection by antivirus engines.
W32/Rustock uses various obfuscation techniques to avoid detection by virus scanners or host-based intrusion prevention systems, making removal difficult.† Once infected, the trojan may disguises itself as a legitimate service.† An unauthenticated, remote attacker could use infected systems as a covert proxy to send spam e-mails or other such malicious activities.
Rule-based and application-based firewalls are likely to prevent or limit the impact of this trojan.† Rule-based firewalls are typically set up by an administrator for an entire network.† These firewalls are often set up to block all traffic entering and exiting a network except traffic traveling through ports needed for production.† Application-based firewalls are often found on client systems and can be configured to allow certain services and process to access the Internet or local network.† These firewalls can be configured to prompt a user each time a new process or service is attempting to access the Internet or local network.† Both types of firewalls may prevent malicious code from downloading updates or additional files.† The firewalls may also prevent the malicious code from contacting an attacker or website and from accessing local network resources.
Most host intrusion detection/prevention system software, such as Cisco Security Agent, can be configured to warn users when suspicious activity occurs on their systems.† This software can be configured to prevent this trojan from attempting to execute their infection routines.† Host intrusion detection/prevention system software may also be configured to prompt a user when suspicious activity occurs.† Often users can choose whether to allow or deny the activity in question.† These factors will limit the infection rate and impact on most systems.
Security best practices dictate that administrators should restrict file formats commonly associated with malicious code from entering the corporate network.† User education focused on avoiding malicious code attacks and responding in the case of infection is of equal importance.
Develop and maintain corporate policies and procedures to mitigate the risk of malicious code.
Block all file attachments except those specifically required for business purposes.
Use current and well-configured antivirus products at multiple levels in the environment. Configure antivirus products to scan all files and provide full-time or auto-protect functions. Configure antivirus products to scan three levels deep on compressed files.
Configure auto-update features to update daily or manually update antivirus signatures. Establish procedures for immediate antivirus updating in response to high-risk malicious code outbreaks.
Conservatively configure mail perimeter servers, routers, firewalls, and personal computers. Disable all unnecessary products, features, and sharing. Install all security-relevant patches and upgrades as available.
Configure network access controls to establish a default deny posture by limiting incoming and outgoing traffic and limiting network services to those required for business operations only.
Establish supplemental protection for remote and mobile users. Include daily updated antivirus, personal firewalls, and network address translation on corporate routers or firewalls.
Provide initial and continuing education to all levels of users throughout the organization.
Users are advised not to open e-mail messages from untrusted sources. Users are advised to verify the authenticity of unexpected files from trusted sources.
Users are advised to use caution when downloading and installing software.
The Microsoft Virus Analysis for W32/Rustock is available at the following link: Virus Description. The latest definitions for the Microsoft products are available at the following link: Microsoft Malware Protection Center.