Submission Summary:

• Submission details:
• Submission received: 14 December 2007, 11:26:34
• Processing time: 3 min 19 sec
• Submitted sample:
• File MD5: 0xCC37B5BE8E352D673D338B4656EFFAA7
• Filesize: 1,407,593 bytes
• Alias: W32.Spybot.Worm [Symantec]

• Summary of the findings:

What's been found	Severity Level
Is protected with Themida in order to prevent the sample from being reverse-engineered. Themida protection can potentially be used by a threat to complicate the manual threat analysis (e.g. the sample would not run under the Virtual Machine).
A network-aware worm that uses known exploit(s) in order to replicate across vulnerable networks.
MS03-026: DCOM RPC Interface Buffer Overrun Vulnerability - replication across TCP 135/139/445/593 (common for Spybot, Randex, other IRC Bots).
MS04-012: DCOM RPC Overflow exploit - replication across TCP 135/139/445/593 (common for Blaster, Welchia, Spybot, Randex, other IRC Bots).
MS04-011: LSASS Overflow exploit - replication across TCP 445 (common for Sasser, Bobax, Kibuv, Korgo, Gaobot, Spybot, Randex, other IRC Bots).
Capability to perform DoS attacks against other computers.
Replication across networks by exploiting weekly restricted shares (common for Randex family of worms).
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 categories were identified:

Threat Category	Description
	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 file was created in the system:

#	Filename(s)	File Size	File Hash	Alias
1	%System%\vbcjlg.exe	1,407,593 bytes	MD5: 0xCC37B5BE8E352D673D338B4656EFFAA7	W32.Spybot.Worm [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
vbcjlg.exe	%System%\vbcjlg.exe	3,096,576 bytes
[filename of the sample #1]	[file and pathname of the sample #1]	3,096,576 bytes

Registry Modifications

• The following Registry Key was created:
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunServices

• The newly created Registry Values are:
• [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
• Microsoft Updater = "vbcjlg.exe"

so that vbcjlg.exe runs every time Windows starts

• [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunServices]
• Microsoft Updater = "vbcjlg.exe"

so that vbcjlg.exe runs every time Windows starts

• [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run]
• Microsoft Updater = "vbcjlg.exe"

so that vbcjlg.exe runs every time Windows starts

Other details

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

• The following ports were open in the system:

• The following Host Names were requested from a host database:
• thisiswhyimh4x.no-ip.biz
• 127.0.0.2
• 127.0.x.x
• 127.0.37.116
• 127.0.36.93

• There were registered attempts to establish connection with the remote hosts. The connection details are:

Outbound traffic (potentially malicious)

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

Heuristics Analysis

• Heuristically identified capability of spreading across the following weakly restricted network shares:

• The network replication uses a dictionary attack by probing credentials from the following list: