Submission Summary:

• Submission details:
• Submission received: 15 July 2012, 08:28:22
• Processing time: 9 min 52 sec
• Submitted sample:
• File MD5: 0x861DF3E4805D3501FFBF74709F087E0B
• File SHA-1: 0x4A1269AE2CED59A4182668189212EEAACCBDEECD
• Filesize: 56,758 bytes
• Alias:
• Backdoor.Bifrose [Symantec]
• BackDoor-CEP.gen.cm [McAfee]
• Mal/Bifrose-X [Sophos]
• Virus.Win32.Bifrose [Ikarus]

• 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	%AppData%\addons.dat	24,758 bytes	MD5: 0xEF608002D3297E1B51B2B53200337F34 SHA-1: 0xC232338F60018F31A2EE3CB99F4F8DBBEF6465A8	(not available)
2	%ProgramFiles%\Bifrost\logg.dat	0 bytes	MD5: 0xD41D8CD98F00B204E9800998ECF8427E SHA-1: 0xDA39A3EE5E6B4B0D3255BFEF95601890AFD80709	(not available)
3	%ProgramFiles%\Bifrost\server.exe	56,758 bytes	MD5: 0x861DF3E4805D3501FFBF74709F087E0B SHA-1: 0x4A1269AE2CED59A4182668189212EEAACCBDEECD	Backdoor.Bifrose [Symantec] BackDoor-CEP.gen.cm [McAfee] Mal/Bifrose-X [Sophos] Virus.Win32.Bifrose [Ikarus]

• Notes:
• %AppData% is a variable that refers to the file system directory that serves as a common repository for application-specific data. A typical path is C:\Documents and Settings\[UserName]\Application Data.
• %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	35,168 bytes
[filename of the sample #1]	[file and pathname of the sample #1]	35,168 bytes

Registry Modifications

• The following Registry Keys were created:
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{7839683A-9D6A-3987-7A1A-1AD96C66CDD3}
• 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\{7839683A-9D6A-3987-7A1A-1AD96C66CDD3}]
• 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
• plg1 = EA 44 DC 02 A3 27 D7 5F 11 AD B9 07 DA F2 35 03 2A 35 8E 58 1B 0E 11 94 D4 F9 28 1F 11 4D 98 BC D2 64 44 8E CD F9 B9 BA 23 BD 45 ED 15 A6 77 AF B8 7C 04 4D 90 91 58 5F 81 61 19 72 00 4E 53 7A E1 AB E6 8B 30 CA 34 56 F9 AD AD F8 4D 41 0F F6 9F 90 A2 1

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:
• shado.servemp3.com
• shado.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: