ThreatExpert Report: Rootkit.Win32.Agent.gw, BackDoor-DLP.sys

Submission Summary:

Submission details:

Submission received: 2 December 2007, 21:07:01
Processing time: 3 min 12 sec
Submitted sample:

File MD5: 0x9419EDC58C2B46A2AF81B55387290883
Filesize: 113,772 bytes

Summary of the findings:

What's been found	Severity Level
Downloads/requests other files from Internet.
Creates a startup registry entry.
Contains characteristics of an identified security risk.

Technical Details:

Possible Security Risk

Attention! The following threat category was identified:

Threat Category	Description
	A code with the rootkit-specific techniques designed to hide the software presence in the system

File System Modifications

The following files were created in the system:

#	Filename(s)	File Size	File Hash	Alias
1	%Temp%\iimo.tmp	113,772 bytes	MD5: 0x218A5AE7E8986DE5081782EA8EA52C51	(not available)
2	%Windir%\new.bat	46 bytes	MD5: 0xF91FB9AC33881E4025F77E2C530E1285	(not available)
3	%Windir%\OLEPRO.dll	75,264 bytes	MD5: 0xD340D67234D7798B059ADFF9D9F6137C	(not available)
4	%System%\drivers\iimo.sys	9,280 bytes	MD5: 0x70C8724F856B3F84D3233665193048CF	Rootkit.Win32.Agent.gw [Kaspersky Lab] BackDoor-DLP.sys [McAfee]
5	%Windir%\vmnat.exe	113,772 bytes	MD5: 0x9419EDC58C2B46A2AF81B55387290883	(not available)

Notes:

%Temp% is a variable that refers to the temporary folder in the short path form. By default, this is C:\Documents and Settings\[UserName]\Local Settings\Temp\ (Windows NT/2000/XP).
%Windir% is a variable that refers to the Windows installation folder. By default, this is C:\Windows or C:\Winnt.
%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
[filename of the sample #1]	[file and pathname of the sample #1]	180,224 bytes
vmnat.exe	%Windir%\vmnat.exe	180,224 bytes

The following module was loaded into the address space of other process(es):

Module Name	Module Filename	Address Space Details
OLEPRO.dll	%Windir%\OLEPRO.dll	Process name: explorer.exe Process filename: %Windir%\explorer.exe Address space: 0x18A0000 - 0x18DF000

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

Driver Name	Driver Filename
iimo.sys	%System%\drivers\iimo.sys

Attention! The following kernel-mode system service functions were hooked:

System Call	Driver name	Driver Filename
NtDeviceIoControlFile	(not recognised)	(not recognised)
NtEnumerateKey	(not recognised)	(not recognised)
NtEnumerateValueKey	(not recognised)	(not recognised)
NtQueryDirectoryFile	(not recognised)	(not recognised)
NtQuerySystemInformation	(not recognised)	(not recognised)

Registry Modifications

The following Registry Keys were created:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\Run
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\ipmone
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\ipmone\Security
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\ipmone\Enum
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ipmone
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ipmone\Security
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ipmone\Enum

The newly created Registry Values are:

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

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

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\ipmone\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\ipmone]

Type = 0x00000001
Start = 0x00000003
ErrorControl = 0x00000001
ImagePath = "\??\%System%\drivers\iimo.sys"
DisplayName = "ipmone"

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

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

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ipmone\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\ipmone]

Type = 0x00000001
Start = 0x00000003
ErrorControl = 0x00000001
ImagePath = "\??\%System%\drivers\iimo.sys"
DisplayName = "ipmone"

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

iimo = "%Windir%\vmnat.exe"

so that vmnat.exe runs every time Windows starts

The following Registry Value was modified:

[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows]

load = "%Windir%\vmnat.exe"

so that vmnat.exe runs every time Windows 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:

EXEONLYONE

The following Host Name was requested from a host database:

www.dellpc.us

The following Internet Connection was established:

Server Name	Server Port	Connect as User	Connection Password
www.dellpc.us	80	(null)	(null)

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.