ThreatExpert Report: Infostealer.Gampass, Trojan-GameThief.Win32.OnLineGames.thlh, New Malware.aj..

Visit ThreatExpert web site

Close Report

Submission Summary:

Submission details:

Submission received: 18 September 2008, 00:25:57
Processing time: 4 min 33 sec
Submitted sample:

File MD5: 0x3138BED1A36A88E60CFBFD196785409E
File SHA-1: 0xC473C81AF8C62BF4B843085C47BC1123528A1EA6
Filesize: 16,701 bytes
Alias:

Infostealer.Gampass [Symantec]
Trojan-GameThief.Win32.OnLineGames.thlh [Kaspersky Lab]
New Malware.aj [McAfee]

Summary of the findings:

What's been found	Severity Level
Creates a startup registry entry.
Uses the AppInit_DLLs value in order to install a module that will be loaded into the address space of every running application.
Packed with a packer that is known to be used by malware (e.g. to complicate threat analysis or detection).
Contains characteristics of an identified security risk.

Technical Details:

Possible Security Risk

Attention! Characteristics of the following security risk was identified in the system:

Security Risk	Description
Adware.Component.Unrelated	These common components have files and keys that are in different threats but the threats are not related to one another in that the author of the signature is not the same. It is recommended that all these entries be removed.

Attention! The following threat categories were identified:

Threat Category	Description
	A malicious backdoor trojan that runs in the background and allows remote access to the compromised system
	A keylogger program that can capture all user keystrokes (including confidential details such username, password, credit card number, etc.)

File System Modifications

The following files were created in the system:

#	Filename(s)	File Size	File Hash	Alias
1	%System%\drivers\HBKernel32.sys	14,640 bytes	MD5: 0xC0ECC24C16F4D0C438931928AED4C483 SHA-1: 0x61346247B5CB81F025693EBBC96144F9EC193ABB	Infostealer.Gampass [Symantec] Backdoor.Win32.Agent.rnq [Kaspersky Lab] TSPY_SYSTEMHI.CL [Trend Micro] PWS:Win32/Lolyda.K [Microsoft]
2	%System%\HBSOUL.dll	24,576 bytes	MD5: 0x5A60F615A54AEFF4C6E71A6ED2FB942E SHA-1: 0x7A7CCCEE2D3B5D026BBDC47972C9FBECECB8F130	Infostealer.Gampass [Symantec]
3	[file and pathname of the sample #1]	16,701 bytes	MD5: 0x3138BED1A36A88E60CFBFD196785409E SHA-1: 0xC473C81AF8C62BF4B843085C47BC1123528A1EA6	Infostealer.Gampass [Symantec] Trojan-GameThief.Win32.OnLineGames.thlh [Kaspersky Lab] New Malware.aj [McAfee]
4	%System%\System.exe	5,120 bytes	MD5: 0x2FC7CE087FC7C8847C1DE12BA5CA14D8 SHA-1: 0x6C675C9D595B3C8009ECD0301D3827709E4CBBF0	Infostealer.Gampass [Symantec]

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).

Memory Modifications

There were new processes created in the system:

Process Name	Process Filename	Main Module Size
System.exe	%System%\system.exe	16,384 bytes
[filename of the sample #1]	[file and pathname of the sample #1]	118,784 bytes

The following modules were loaded into the address space of other process(es):

Module Name	Module Filename	Address Space Details
HBSOUL.dll	%System%\HBSOUL.dll	Process name: System.exe Process filename: %System%\system.exe Address space: 0x830000 - 0x836000
HBSOUL.dll	%System%\HBSOUL.dll	Process name: IEXPLORE.EXE Process filename: %ProgramFiles%\internet explorer\iexplore.exe Address space: 0x10000000 - 0x10006000

Notes:

%ProgramFiles% is a variable that refers to the Program Files folder. A typical path is C:\Program Files.

There was a new kernel-mode driver installed in the system:

Driver Name	Driver Filename
HBKernel32 Driver	%System%\Drivers\HBKernel32.sys

Registry Modifications

The following Registry Keys were created:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_HBKERNEL32
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_HBKERNEL32\0000
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_HBKERNEL32\0000\Control
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\HBKernel32
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\HBKernel32\Security
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\HBKernel32\Enum
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\HBKernel32
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_HBKERNEL32
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_HBKERNEL32\0000
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_HBKERNEL32\0000\Control
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HBKernel32
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HBKernel32\Security
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HBKernel32\Enum

The newly created Registry Values are:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]

HBService32 = "System.exe"

so that System.exe runs every time Windows starts

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_HBKERNEL32\0000\Control]

*NewlyCreated* = 0x00000000
ActiveService = "HBKernel32"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_HBKERNEL32\0000]

Service = "HBKernel32"
Legacy = 0x00000001
ConfigFlags = 0x00000000
Class = "LegacyDriver"
ClassGUID = "{8ECC055D-047F-11D1-A537-0000F8753ED1}"
DeviceDesc = "HBKernel32 Driver"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_HBKERNEL32]

NextInstance = 0x00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\HBKernel32\Enum]

0 = "Root\LEGACY_HBKERNEL32\0000"
Count = 0x00000001
NextInstance = 0x00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\HBKernel32\Security]

Security = 01 00 14 80 90 00 00 00 9C 00 00 00 14 00 00 00 30 00 00 00 02 00 1C 00 01 00 00 00 02 80 14 00 FF 01 0F 00 01 01 00 00 00 00 00 01 00 00 00 00 02 00 60 00 04 00 00 00 00 00 14 00 FD 01 02 00 01 01 00 00 00 00 00 05 12 00 00 00 00 00 18 00 FF 01 0F 0

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\HBKernel32]

Type = 0x00000001
Start = 0x00000000
ErrorControl = 0x00000000
ImagePath = "%System%\Drivers\HBKernel32.sys"
DisplayName = "HBKernel32 Driver"
Group = "Boot Bus Extender"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\HBKernel32]

DisplayName = "HBKernel32 Driver"
ErrorControl = 0x00000000
ImagePath = "%System%\Drivers\HBKernel32.sys"
Start = 0x00000000
Type = 0x00000001
Group = "Boot Bus Extender"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_HBKERNEL32\0000\Control]

*NewlyCreated* = 0x00000000
ActiveService = "HBKernel32"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_HBKERNEL32\0000]

Service = "HBKernel32"
Legacy = 0x00000001
ConfigFlags = 0x00000000
Class = "LegacyDriver"
ClassGUID = "{8ECC055D-047F-11D1-A537-0000F8753ED1}"
DeviceDesc = "HBKernel32 Driver"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_HBKERNEL32]

NextInstance = 0x00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HBKernel32\Enum]

0 = "Root\LEGACY_HBKERNEL32\0000"
Count = 0x00000001
NextInstance = 0x00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HBKernel32\Security]

Security = 01 00 14 80 90 00 00 00 9C 00 00 00 14 00 00 00 30 00 00 00 02 00 1C 00 01 00 00 00 02 80 14 00 FF 01 0F 00 01 01 00 00 00 00 00 01 00 00 00 00 02 00 60 00 04 00 00 00 00 00 14 00 FD 01 02 00 01 01 00 00 00 00 00 05 12 00 00 00 00 00 18 00 FF 01 0F 0

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HBKernel32]

Type = 0x00000001
Start = 0x00000000
ErrorControl = 0x00000000
ImagePath = "%System%\Drivers\HBKernel32.sys"
DisplayName = "HBKernel32 Driver"
Group = "Boot Bus Extender"

The following Registry Value was modified:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows]

AppInit_DLLs = "HBmhly.dll,HB1000Y.dll,HBWOOOL.dll,HBXY2.dll,HBJXSJ.dll,HBSO2.dll,HBFS2.dll,HBXY3.dll,HBSHQ.dll,HBFY.dll,HBWULIN2.dll,HBW2I.dll,HBKDXY.dll,HBWORLD2.dll,HBASKTAO.dll,HBZHUXIAN.dll,HBWOW.dll,HBZERO.dll,HBBO.dll,HBCONQUER.dll,HBSOUL.dll,HBCHIBI.dll,HBD

so that HBSOUL.dll runs every time a Windows application starts

Other details

Analysis of the file resources indicate the following possible country of origin:

China

To mark the presence in the system, the following Mutex object was created:

HBInjectMutex

There was application-defined hook procedure installed into the hook chain (e.g. to monitor keystrokes). The installed hook is handled by the following module:

%System%\HBSOUL.dll

the hook is handled by its export "_ServiceRouteEx@12()"

All content ("Information") contained in this report is the copyrighted work of Threat Expert Ltd and its associated companies ("ThreatExpert") and may not be copied without the express permission of ThreatExpert.

The Information is provided on an "as is" basis. ThreatExpert disclaims all warranties, whether express or implied, to the maximum extent permitted by law, including the implied warranties that the Information is merchantable, of satisfactory quality, accurate, fit for a particular purpose or need, or non-infringing, unless such implied warranties are legally incapable of exclusion. Further, ThreatExpert does not warrant or make any representations regarding the use or the results of the use of the Information in terms of their correctness, accuracy, reliability, or otherwise.