Submission Summary:

• Submission details:
• Submission received: 5 June 2008, 00:42:22
• Processing time: 4 min 44 sec
• Submitted sample:
• File MD5: 0xD4EDF4D8E90BDF549B914C8F4253B6D4
• File SHA-1: 0x497883C0F533EF0B978CE038CE202BAA66B8E49B
• Filesize: 141,824 bytes
• Alias: Trojan.Peacomm.D [Symantec]

• Summary of the findings:

What's been found	Severity Level
Threat characteristics of the Storm worm (aka CME-711/Peacomm/Nuwar/Zhelatin/Tibs). This threat is normally received as an email attachment; it may consist of a rootkit, a peer-to-peer client, and a mass-mailing worm component. To bypass firewalls, its code may be injected and run from the legitimate services.exe process.
Capability to send out email message(s) with the built-in SMTP client engine.
Searching for email addresses by enumerating files with the certain extensions. This functionality is used by mass-mailers and spam-bots.
Backdoor functionality: connected remote users are able to perform multiple actions on the compromised system.
Downloads/requests other files from Internet.
Creates a startup registry entry.
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
Email-Worm.Zhelatin	Email-Worm.Zhelatin normally received as an email attachment; may consist of a rootkit, a peer-to-peer client, and a mass-mailing worm component. Its code may be injected and run from the legitimate services.exe process in order to bypass firewalls.

• 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 network-aware worm that attempts to replicate across the existing network(s)
	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	%Windir%\grinders.config	46,262 bytes	MD5: 0xDF8B222EF27710C0B7C5E82E1877F7C0 SHA-1: 0x835D23A94F904A3F11E4B51C412A3B2F4DD3FF1C	(not available)
2	%Windir%\grinders.exe [file and pathname of the sample #1]	141,824 bytes	MD5: 0xD4EDF4D8E90BDF549B914C8F4253B6D4 SHA-1: 0x497883C0F533EF0B978CE038CE202BAA66B8E49B	Trojan.Peacomm.D [Symantec]

• Note:
• %Windir% is a variable that refers to the Windows installation folder. By default, this is C:\Windows or C:\Winnt.

Memory Modifications

• There were new processes created in the system:

Process Name	Process Filename	Main Module Size
grinders.exe	%Windir%\grinders.exe	151,552 bytes
[filename of the sample #1]	[file and pathname of the sample #1]	151,552 bytes

Registry Modifications

• The newly created Registry Values are:
• [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\ITStorage\Finders]
• ID = 0x6AE61F3C
• [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run]
• grinders = "%Windir%\grinders.exe"

so that grinders.exe runs every time Windows starts

Other details

• The following ports were open in the system:

• The following Internet Connection was established:

Heuristics Analysis

• Heuristically identified details of the peer-to-peer botnet that could be used to download the latest instructions: