Submission Summary:

• Submission details:
• Submission received: 11 September 2012, 18:12:06
• Processing time: 7 min 47 sec
• Submitted sample:
• File MD5: 0xAE77ED90CA641B80C1957AF037A1CEFC
• File SHA-1: 0x2F8AB0264EA5832D0F86F40A93ABD1ABADA6B4A4
• Filesize: 218,426 bytes
• Alias:
• Trojan.Dropper [Symantec]
• Trojan.Win32.Refroso.bttu [Kaspersky Lab]
• Generic BackDoor.aag [McAfee]
• Mal/Bifrose-Z [Sophos]
• Backdoor:Win32/Bifrose.AE [Microsoft]
• Backdoor.Win32.Bifrose [Ikarus]
• Win-Trojan/Refroso.218426 [AhnLab]

• Summary of the findings:

What's been found	Severity Level
Produces outbound traffic.
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
Backdoor.Bifrose	Backdoor.Bifrose is a backdoor trojan that attempts to propagate by exploiting local network shares. It will also attempt to join a predefined IRC server and channel in order to participate in DDoS attacks.

• 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	%System%\Bifrost\logg.dat	0 bytes	MD5: 0xD41D8CD98F00B204E9800998ECF8427E SHA-1: 0xDA39A3EE5E6B4B0D3255BFEF95601890AFD80709	(not available)
2	%System%\Bifrost\Server.exe [file and pathname of the sample #1]	218,426 bytes	MD5: 0xAE77ED90CA641B80C1957AF037A1CEFC SHA-1: 0x2F8AB0264EA5832D0F86F40A93ABD1ABADA6B4A4	Trojan.Dropper [Symantec] Trojan.Win32.Refroso.bttu [Kaspersky Lab] Generic BackDoor.aag [McAfee] Mal/Bifrose-Z [Sophos] Backdoor:Win32/Bifrose.AE [Microsoft] Backdoor.Win32.Bifrose [Ikarus] Win-Trojan/Refroso.218426 [AhnLab]

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

• The following directory was created:
• %System%\Bifrost

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]	98,304 bytes
server.exe	%System%\bifrost\server.exe	98,304 bytes

Registry Modifications

• The following Registry Keys were created:
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{9D71D88C-C598-4935-C5D1-43AA4DB90836}
• HKEY_LOCAL_MACHINE\SOFTWARE\Bifrost
• HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\MediaResources\msvideo
• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaResources\msvideo
• HKEY_CURRENT_USER\Software\Bifrost

• The newly created Registry Values are:
• [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{9D71D88C-C598-4935-C5D1-43AA4DB90836}]
• stubpath = "%System%\Bifrost\Server.exe s"

so that Server.exe runs every time Windows starts

• [HKEY_LOCAL_MACHINE\SOFTWARE\Bifrost]
• nck = ED 1B E6 27 B9 28 D6 32 74 C3 CD 74 FA 93 5B 67
• [HKEY_CURRENT_USER\Software\Bifrost]
• klg = 01

Other details

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

• The following Host Name was requested from a host database:
• broken9111.no-ip.biz

• There was registered attempt to establish connection with the remote host. The connection details are:

• 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:
• %ProgramFiles%\Internet Explorer\iexplore.exe

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

Outbound traffic (potentially malicious)

• There was an outbound traffic produced on port 81: