Submission Summary:

• Submission details:
• Submission received: 6 April 2009, 15:41:25
• Processing time: 6 min 57 sec
• Submitted sample:
• File MD5: 0xB82888D7BB3FB6D1AD08B5EC8C8DE333
• File SHA-1: 0xEB2B703AC7F3A5CDBAB51FDFDA445148DE245F32
• Filesize: 186,128 bytes
• Alias:
• Worm.Hamweg.Gen [PCTools]
• Worm.Win32.Hamweq [Ikarus]

• Summary of the findings:

What's been found	Severity Level
Creates desktop.ini system file in the fake Recycle Bin folder in order to register it in Windows as a valid Recycle Bin.
Creates an executable file in the fake Recycle Bin folder with the purpose of concealing its presence in the system.
Creates fake Recycle Bin folder.
Communication with a remote IRC server.
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 malicious trojan horse or bot that may represent security risk for the compromised system and/or its network environment

File System Modifications

• The following files were created in the system:

#	Filename(s)	File Size	File Hash	Alias
1	%Temp%\autorun.inf	248 bytes	MD5: 0xC3191EFB5935DA19209D7D509B74BCFB SHA-1: 0xB0C09B0483F178692E948D0E8E51616EB392731D	W32/HostInf-A [Sophos]
2	%Temp%\msvcr71.dll	348,160 bytes	MD5: 0x86F1895AE8C5E8B17D99ECE768A70732 SHA-1: 0xD5502A1D00787D68F548DDEEBBDE1ECA5E2B38CA	(not available)
3	%Temp%\RECYCLER\k-1-3542-4232123213-7676767-8888886\Desktop.ini %Temp%\RECYCLER\S-1-5-21-1482476501-1644491937-682003330-1013\Desktop.ini c:\RECYCLER\k-1-3542-4232123213-7676767-8888886\Desktop.ini	62 bytes	MD5: 0x7457A5DF1FF47C957ACF1FA000D7D9AD SHA-1: 0x69D2BBA827FD4DE0169419A0FDA280252B348514	(not available)
4	%Temp%\RECYCLER\k-1-3542-4232123213-7676767-8888886\xv.exe c:\RECYCLER\k-1-3542-4232123213-7676767-8888886\xv.exe	12,800 bytes	MD5: 0xCEEBE88231D161C821CC5CA476C5A906 SHA-1: 0x908A15D133C2D345930C1CA22CEAC551956E1CCE	Worm.Hamweg.Gen [PCTools] W32/Autoham-Fam [Sophos] Worm:Win32/Hamweq.A [Microsoft] Worm.Win32.Hamweq [Ikarus] Win-Trojan/Hamweq.12800 [AhnLab]
5	%Temp%\RECYCLER\S-1-6-21-2438476501-1644491937-701003331-1213\Desktop.ini	63 bytes	MD5: 0xE783BDD20A976EAEAAE1FF4624487420 SHA-1: 0xC2A44FAB9DF00B3E11582546B16612333C2F9286	(not available)
6	[file and pathname of the sample #1]	186,128 bytes	MD5: 0xB82888D7BB3FB6D1AD08B5EC8C8DE333 SHA-1: 0xEB2B703AC7F3A5CDBAB51FDFDA445148DE245F32	Worm.Hamweg.Gen [PCTools] Worm.Win32.Hamweq [Ikarus]

• Note:
• %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).

• The following directories were created:
• %Temp%\RECYCLER
• %Temp%\System
• %Temp%\RECYCLER\k-1-3542-4232123213-7676767-8888886
• %Temp%\RECYCLER\S-1-5-21-1482476501-1644491937-682003330-1013
• %Temp%\RECYCLER\S-1-6-21-2438476501-1644491937-701003331-1213
• %Temp%\RECYCLER\S-5-3-42-2819952290-8240758988-879315005-3665
• %Temp%\System\Security
• c:\RECYCLER\k-1-3542-4232123213-7676767-8888886

Memory Modifications

• There were new processes created in the system:

Process Name	Process Filename	Main Module Size
[generic host process]	[generic host process filename]	20,480 bytes
xv.exe	%Temp%\RECYCLER\k-1-3542-4232123213-7676767-8888886\xv.exe	20,480 bytes

• Notes:
• [generic host process filename] is a full path filename of [generic host process].

Registry Modifications

• The following Registry Key was created:
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{26KLN5J0-4OPX-11WE-AAX3-24EF1F387272}

• The newly created Registry Value is:
• [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{26KLN5J0-4OPX-11WE-AAX3-24EF1F387272}]
• StubPath = "c:\RECYCLER\k-1-3542-4232123213-7676767-8888886\xv.exe"

so that xv.exe runs every time Windows starts

Other details

• The following Host Name was requested from a host database:
• unixdevelopemnt.info

Outbound traffic (potentially malicious)

• Attention! There was a new connection established with a remote IRC Server. The generated outbound IRC traffic is provided below: