Analysis by: Anthony Joe Melgarejo
ALIASES:

VirTool:Win32/CeeInject.gen!ID (Microsoft), Infostealer (Symantec), PWS-Zbot.gen.anm (McAfee)

 PLATFORM:

Windows 2000, Windows XP, Windows Server 2003

 OVERALL RISK RATING:
 REPORTED INFECTION:
 SYSTEM IMPACT RATING:
 INFORMATION EXPOSURE:

  • Threat Type: Spyware

  • Destructiveness: No

  • Encrypted: Yes

  • In the wild: Yes

  OVERVIEW

This spyware arrives on a system as a file dropped by other malware or as a file downloaded unknowingly by users when visiting malicious sites.

It deletes the initially executed copy of itself.

  TECHNICAL DETAILS

File Size: 132967 bytes
File Type: EXE
Memory Resident: Yes
Initial Samples Received Date: 23 Sep 2012

Arrival Details

This spyware arrives on a system as a file dropped by other malware or as a file downloaded unknowingly by users when visiting malicious sites.

Installation

This spyware drops the following copies of itself into the affected system and executes them:

  • %User Profile%\Application Data\KB{random number}.exe

(Note: %User Profile% is the current user's profile folder, which is usually C:\Windows\Profiles\{user name} on Windows 98 and ME, C:\WINNT\Profiles\{user name} on Windows NT, and C:\Documents and Settings\{user name} on Windows 2000, XP, and Server 2003.)

Autostart Technique

This spyware adds the following registry entries to enable its automatic execution at every system startup:

HKEY_CURRENT_USER\Software\Microsoft\
Windows\CurrentVersion\Run
KB{random number}.exe = "%User Profile%\Application Data\KB{random number}.exe"

Other System Modifications

This spyware adds the following registry keys:

HKEY_CURRENT_USER\Software\Microsoft\
Windows NT\{random hex string 1}

HKEY_CURRENT_USER\Software\Microsoft\
Windows NT\{random hex string 2}

It adds the following registry entries:

HKEY_CURRENT_USER\Software\Microsoft\
Windows\CurrentVersion\Internet Settings
GlobalUserOffline = "0"

Other Details

This spyware connects to the following possibly malicious URL:

  • http://{random IP address}:8080/mx5/B/in/

It deletes the initially executed copy of itself

  SOLUTION

Minimum Scan Engine: 9.200
FIRST VSAPI PATTERN FILE: 9.456.04
FIRST VSAPI PATTERN DATE: 23 Sep 2012
VSAPI OPR PATTERN File: 9.457.00
VSAPI OPR PATTERN Date: 24 Sep 2012

Step 1

For Windows XP and Windows Server 2003 users, before doing any scans, please make sure you disable System Restore to allow full scanning of your computer.

Step 2

Restart in Safe Mode

[ Learn More ]

Step 3

Delete this registry key

[ Learn More ]

Important: Editing the Windows Registry incorrectly can lead to irreversible system malfunction. Please do this step only if you know how or you can ask assistance from your system administrator. Else, check this Microsoft article first before modifying your computer's registry.

  • In HKEY_CURRENT_USER\Software\Microsoft\Windows NT
    • {random hex string 1}
  • In HKEY_CURRENT_USER\Software\Microsoft\Windows NT
    • {random hex string 2}

Step 4

Delete this registry value

[ Learn More ]

Important: Editing the Windows Registry incorrectly can lead to irreversible system malfunction. Please do this step only if you know how or you can ask assistance from your system administrator. Else, check this Microsoft article first before modifying your computer's registry.

 
  • In HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
    • KB{random number}.exe = "%User Profile%\Application Data\KB{random number}.exe"
  • In HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings
    • GlobalUserOffline = "0"

Step 5

Restart in normal mode and scan your computer with your Trend Micro product for files detected as TSPY_ZBOT.CXS. If the detected files have already been cleaned, deleted, or quarantined by your Trend Micro product, no further step is required. You may opt to simply delete the quarantined files. Please check this Knowledge Base page for more information.

NOTES:

The created registry keys HKEY_CURRENT_USER\Software\Microsoft\Windows NT\{random hex string 1} and HKEY_CURRENT_USER\Software\Microsoft\Windows NT\{random hex string 2} cannot be identified by the users since there are no reference values in the created keys. The only way these keys can be identified is by comparing the present keys with a backup if the users have one. Note that these keys need not to be deleted since it won't cause the user system any harm.


Did this description help? Tell us how we did.