Where to Buy Trend Micro Products

For Home

For Small Business

1-888-762-8736
(M-F 8:00am-5:00pm CST)

For Enterprise

1-877-218-7353
(M-F 8:00am-5:00pm CST)

Not in the United States?
Select the country/language of your choice:

Asia Pacific Region

Europe

The Americas

Not in the United States?
Select the country/language of your choice:

Asia/Pacific

Europe

America

Login

For Home

For Business

For Partners

Threat Encyclopedia

TSPY_ZBOT.JMO

ANALYSIS BY

Cris Nowell Pantanilla


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

Infection Channel:

Downloaded from the Internet, Dropped by other malware


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 is injected into all running processes to remain memory resident.

It modifies the Internet Explorer Zone Settings.

As of this writing, the said sites are inaccessible.

TECHNICAL DETAILS

File Size:

347,112 bytes

File Type:

EXE

Memory Resident:

Yes

Initial Samples Received Date:

23 Jun 2012

Payload:

Downloads files

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:

  • %User Profile%\Application Data\{random1}\{random}.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.)

It drops the following files:

  • %User Profile%\Application Data\{random2}\{random}.{random}
  • %User Profile%\Application Data\Microsoft\Address Book\winxp.wab
  • %User Profile%\Application Data\Microsoft\Address Book\winxp.wab~
  • %Application Data%\Identities\{CLSID}\Microsoft\Outlook Express\Folders.dbx
  • %Application Data%\Identities\{CLSID}\Microsoft\Outlook Express\Inbox.dbx
  • %Application Data%\Identities\{CLSID}\Microsoft\Outlook Express\Offline.dbx
  • %Application Data%\Identities\{CLSID}\Microsoft\Outlook Express\Sent Items.dbx

(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.. %Application Data% is the current user's Application Data folder, which is usually C:\Windows\Profiles\{user name}\Application Data on Windows 98 and ME, C:\WINNT\Profiles\{user name}\Application Data on Windows NT, and C:\Documents and Settings\{user name}\Local Settings\Application Data on Windows 2000, XP, and Server 2003.)

It creates the following folders:

  • %User Profile%\Application Data\{random1}
  • %User Profile%\Application Data\{random2}
  • %User Profile%\Application Data\Microsoft\Address Book
  • %Application Data%\Identities
  • %Application Data%\Identities\{CLSID}
  • %Application Data%\Identities\{CLSID}\Microsoft
  • %Application Data%\Identities\{CLSID}\Microsoft\Outlook Express

(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.. %Application Data% is the current user's Application Data folder, which is usually C:\Windows\Profiles\{user name}\Application Data on Windows 98 and ME, C:\WINNT\Profiles\{user name}\Application Data on Windows NT, and C:\Documents and Settings\{user name}\Local Settings\Application Data on Windows 2000, XP, and Server 2003.)

It is injected into all running processes to remain memory resident.

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
{random CLSID} = "%User Profile%\Application Data\{random1}\{random}.exe"

Other System Modifications

This spyware adds the following registry keys:

HKEY_CURRENT_USER\Software\Microsoft\
{random}

HKEY_CURRENT_USER\Software\Microsoft\
WAB

It creates the following registry entry(ies) to bypass Windows Firewall:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\SharedAccess\Parameters\
FirewallPolicy\StandardProfile\AuthorizedApplications\
List
%Windows%\explorer.exe = "%Windows%\explorer.exe:*:Enabled:Windows Explorer"

Web Browser Home Page and Search Page Modification

This spyware modifies the Internet Explorer Zone Settings.

Download Routine

This spyware connects to the following URL(s) to download its configuration file:

  • http://{pseudorandom alpha characters}.biz
  • http://{pseudorandom alpha characters}.org
  • http://{pseudorandom alpha characters}.info
  • http://{pseudorandom alpha characters}.net
  • http://{pseudorandom alpha characters}.com

As of this writing, the said sites are inaccessible.

NOTES:

The URL where it connects to is randomly generated using a randomizing function, which is computed based on the system's current date. The download file is the configuration file that contains the list of sites to be monitored.

The configuration file may contain URLs where it downloads an updated copy of itself and where it sends its gathered information. It may also contain URLs of its target online banking and finance-related sites from where it steals the information.

SOLUTION

Minimum Scan Engine:

9.200

FIRST VSAPI PATTERN FILE:

9.212.04

FIRST VSAPI PATTERN DATE:

23 Jun 2012

VSAPI OPR PATTERN File:

9.213.00

VSAPI OPR PATTERN Date:

24 Jun 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
    • WAB

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
    • {Random CLSID} = "%User Profile%\Application Data\{random1}.exe"
  • In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\AuthorizedApplications\List
    • %Windows%\explorer.exe = "%Windows%\explorer.exe:*:Enabled:Windows Explorer"

Step 5

Search and delete these folders

[ Learn More ]
Please make sure you check the Search Hidden Files and Folders checkbox in the More advanced options option to include all hidden folders in the search result.
  • %User Profile%\Application Data\{random1}
  • %User Profile%\Application Data\{random2}
  • %User Profile%\Application Data\Microsoft\Address Book
  • %Application Data%\Identities

Step 6

Reset Internet security settings

[ Learn More ]

Step 7

Restart in normal mode and scan your computer with your Trend Micro product for files detected as TSPY_ZBOT.JMO. 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 key HKEY_CURRENT_USER\Software\Microsoft\{random} cannot be identified by the user since there are no reference values in the created key. The only way it can be identified is by comparing the present keys with a backup if the users have one. Note that the key need not to be deleted since it does not cause the user system any harm.


Did this description help? Tell us how we did.

Featured Stories

Connect with us on