Malware Analysis Report (AR20-133O)


Click to Tweet.
Click to send to Facebook.
Click to Share.


This report is provided "as is" for informational purposes only. The Department of Homeland Security (DHS) does not provide any warranties of any kind regarding any information contained herein. The DHS does not endorse any commercial product or service referenced in this bulletin or otherwise.

This document is marked TLP:WHITE--Disclosure is not limited. Sources may use TLP:WHITE when information carries minimal or no foreseeable risk of misuse, in accordance with applicable rules and procedures for public release. Subject to standard copyright rules, TLP:WHITE information may be distributed without restriction. For more information on the Traffic Light Protocol (TLP), see



This report contains information obtained from automated analysis and is not intended to be a complete description of the submitted sample. Results may be limited due to the complexity of the samples, or due to the ability of the samples to defend against automated analysis techniques. If additional information is required, please contact the Cybersecurity and Infrastructure Security Agency (CISA) using the information provided at the end of this report.

CISA received one artifact, ff4138ca9119ab0381ad6575f041e633, which appeared to be a crafted RTF document to perform penetration testing for the CVE-2012-0158 vulnerability found in Microsoft Office 2003, 2007 and 2010. It is actually an obfuscated RTF that when opened in Microsoft Word, it connected to and attempted to download an executable named Specification.exe, copied it over to word.scr and executed it immediately. At the time of this analysis, the domain returned HTTP 404 not found to the HTTP GET request.

For a downloadable copy of IOCs, see MIFR-10079683-1.v2.stix.

Files (1)

ebbca8bb8e0812f3f66e905a58800a3410ae26b9e1df233741f72021676360dc (ff4138ca9119ab0381ad6575f041e6...)

Domains (1)

IPs (1)





Name ff4138ca9119ab0381ad6575f041e633
Size 1203123 bytes
Type Rich Text Format data, version 1, unknown character set
MD5 ff4138ca9119ab0381ad6575f041e633
SHA1 a3639691eb5fa1b41225ff35791f9931b62aeacd
SHA256 ebbca8bb8e0812f3f66e905a58800a3410ae26b9e1df233741f72021676360dc
SHA512 42b47b48420367b4d4ce6e94d0d6e776d4ac903873324abd09c4e7776cf0cb5c79796421a6072f5d5624f09eb4080ed69799e6ebb23e68d3cc18f76240c3d1e9
ssdeep 96:GiIH6Q+Y2pbrh8mM/iBq7KWJZ6rBcClgJr3u17ejofQqa5hstzaqiFi12B7FiJi6:GlH6rfh8mQ7KraIwmzOiJN64g6mS12y
Entropy 2.667311
Ahnlab RTF/Exploit
Antiy Trojan[Exploit]/Office.CVE-2012-0158.h
Avira EXP/CVE-2012-0158.TJ
BitDefender Exploit.RTF.CVE-2012-0158.H
ClamAV Rtf.Dropper.Agent-1557037
Emsisoft Exploit.RTF.CVE-2012-0158.H (B)
Ikarus Trojan.Win32.Exploit
McAfee Exploit-CVE2012-0158.w
Microsoft Security Essentials Exploit:Win32/CVE-2012-0158
NANOAV Exploit.Rtf.Heuristic-rtf.dinbqn
Quick Heal Exp.RTF.Obfus.Gen
Sophos Troj/DocDrop-ID
Symantec Trojan.Mdropper
TACHYON Exploit.RTF.CVE-2012-0158.H
TrendMicro TROJ_MD.E9643850
TrendMicro House Call TROJ_MD.E9643850
YARA Rules

No matches found.

ssdeep Matches
99 41bc1f68ca81527487e22bb2bc3db796f5a8724258fc8769a288a6ff0f6875e5
ebbca8bb8e... Connected_To

FF4138CA9119AB0381AD6575F041E633 is an obfuscated RTF document, appeared to be crafted to perform penetration testing when examined under a hexadecimal editor. Close to the end of file, ASCII data "For pentesting purposes only!" and the MD5 hash value of the RTF were found.

However, when the RTF was opened in Microsoft Word, it sent a HTTP GET request to the domain in order to download a binary named Specification.exe. If successfully downloaded it would copy Specification.exe to word.scr and immediately execute it.

When the RTF was examined under a debugger, the location of word.scr was in the C:\Windows\system32 directory; word.scr ran on the system followed by a system crash and reboot. However, when the RTF was opened without a debugger, word.scr was copied to the same directory where RTF was located at and the system did not crash.

At the time of this analysis, returned HTTP 404 Not Found to the HTTP GET request for the Specification.exe binary.

Figure 1 -

Figure 1 -

Figure 2 -

Figure 2 -

Figure 3 -

Figure 3 -