Submission Summary:

• Submission details:
• Submission received: 21 September 2012, 00:11:08
• Processing time: 10 min 34 sec
• Submitted sample:
• File MD5: 0xD6DEAE58A5BD414DF4B6659A6FFE8D15
• File SHA-1: 0x3DC1A6390D6E9D9F9DFC7A84023E85DDBD9DC652
• Filesize: 32,701 bytes
• Alias:
• Backdoor.Trojan [Symantec]
• Backdoor.Win32.Bifrose.fxv [Kaspersky Lab]
• Generic BackDoor.aab [McAfee]
• BKDR_BIFROSE.SMA [Trend Micro]
• Mal/Bifrose-X [Sophos]
• Backdoor:Win32/Bifrose.AE [Microsoft]
• Trojan.Win32.Midgare [Ikarus]
• Win-Trojan/Midgare.30208 [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! The following threat category was identified:

Threat Category	Description
	A malicious backdoor trojan that runs in the background and allows remote access to the compromised system

File System Modifications

• The following files were created in the system:

#	Filename(s)	File Size	File Hash	Alias
1	%ProgramFiles%\Bifrost\logg.dat	0 bytes	MD5: 0xD41D8CD98F00B204E9800998ECF8427E SHA-1: 0xDA39A3EE5E6B4B0D3255BFEF95601890AFD80709	(not available)
2	%ProgramFiles%\Bifrost\server.exe [file and pathname of the sample #1]	32,701 bytes	MD5: 0xD6DEAE58A5BD414DF4B6659A6FFE8D15 SHA-1: 0x3DC1A6390D6E9D9F9DFC7A84023E85DDBD9DC652	Backdoor.Trojan [Symantec] Backdoor.Win32.Bifrose.fxv [Kaspersky Lab] Generic BackDoor.aab [McAfee] BKDR_BIFROSE.SMA [Trend Micro] Mal/Bifrose-X [Sophos] Backdoor:Win32/Bifrose.AE [Microsoft] Trojan.Win32.Midgare [Ikarus] Win-Trojan/Midgare.30208 [AhnLab]

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

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

Memory Modifications

• There were new processes created in the system:

Process Name	Process Filename	Main Module Size
server.exe	%ProgramFiles%\Bifrost\server.exe	36,864 bytes
[filename of the sample #1]	[file and pathname of the sample #1]	36,864 bytes

Registry Modifications

• The following Registry Keys were created:
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{C4845803-1456-C522-8764-3405EBD75C98}
• 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\{C4845803-1456-C522-8764-3405EBD75C98}]
• stubpath = "%ProgramFiles%\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 Names were requested from a host database:
• max15.myftp.biz
• bbox20.no-ip.org

• 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

Outbound traffic (potentially malicious)

• There was an outbound traffic produced on port 81: