Malicious RTF — malware analysis report

Static analysis result for SHA-256 dc7da540ce83cbcb…

MALICIOUS

RTF

919.0 KB Created: 2018-05-10 15:52:00 First seen: 2018-05-18
MD5: 827137fe4802dcd945b5dcef27918761 SHA-1: 14d68767fd11cbad6165b3532ee625ff1ed86526 SHA-256: dc7da540ce83cbcb113bd2472931e492b91eec5dc3a3cc856bc70b9db836fd4f
262 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains multiple embedded OLE objects and triggers an ".objupdate" command, indicating an attempt to activate these objects. The critical heuristic firing for CVE-2017-8759 confirms exploitation of this vulnerability, which is commonly used to download and execute arbitrary code. The embedded URL is suspicious and likely part of the exploit chain.

Heuristics 6

  • CVE-2017-8759 — MSXML SAX OLE activation critical CVE likely CVE_2017_8759
    RTF contains a hex-encoded OLE1 object for Msxml2.SAXXMLReader.6.0 followed by an embedded OLE compound document, and the document requests OLE activation. This matches the RTF staging shape used for CVE-2017-8759 SOAP/WSDL parser code injection.
  • ClamAV: Doc.Dropper.Agent-6412232-1 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Doc.Dropper.Agent-6412232-1
  • \objupdate forces OLE activation high RTF_OBJUPDATE
    RTF contains \objupdate — forces automatic OLE object instantiation when the document is opened, bypassing user interaction. Almost exclusively seen in Equation Editor exploit documents.
  • OLE object data medium RTF_OBJDATA
    RTF contains 10 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://schemas In RTF body

Extracted artifacts 8

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00002c8f.bin rtf-objdata-decoded RTF \objdata at offset 0x2C8F 33339 bytes
SHA-256: 629d64b02682881d97312099e71ee8f7afea11fd7f27c1c0f94745e1969f7236
Detection
ClamAV: Doc.Dropper.Agent-6412232-1
Obfuscation or payload: unlikely
objdata_01_off00018bcc.bin rtf-objdata-decoded RTF \objdata at offset 0x18BCC 33339 bytes
SHA-256: 1daddd205937183729d7030f43c9d7f1dc9eb80dc65ad85ec0f23aeb84e9c736
Detection
ClamAV: Doc.Dropper.Agent-6412232-1
Obfuscation or payload: unlikely
objdata_02_off0002eb09.bin rtf-objdata-decoded RTF \objdata at offset 0x2EB09 33339 bytes
SHA-256: 6a24c3a6f9eb2069ee870bf6f71d55671bb0a011fd150b82de09b9b91441d6f9
Detection
ClamAV: Doc.Dropper.Agent-6412232-1
Obfuscation or payload: unlikely
objdata_03_off00044a46.bin rtf-objdata-decoded RTF \objdata at offset 0x44A46 33339 bytes
SHA-256: 41fdc3b3d7dc6292be56252e97decdc5f381b62fa0d71a3c03aeb0ae91c8f322
Detection
ClamAV: Doc.Dropper.Agent-6412232-1
Obfuscation or payload: unlikely
objdata_06_off00086849.bin rtf-objdata-decoded RTF \objdata at offset 0x86849 33339 bytes
SHA-256: 4c8c17899ca97f94e38d7ede8d07ed845c92226666973bd60bb54ca1d2df9559
Detection
ClamAV: Doc.Dropper.Agent-6412232-1
Obfuscation or payload: unlikely
objdata_07_off0009c786.bin rtf-objdata-decoded RTF \objdata at offset 0x9C786 33339 bytes
SHA-256: d011b8675378cdfd19d88a0566f4ebec2f2dea7e7e6eb3420cb2004ad071051d
Detection
ClamAV: Doc.Dropper.Agent-6412232-1
Obfuscation or payload: unlikely
objdata_08_off000b26c3.bin rtf-objdata-decoded RTF \objdata at offset 0xB26C3 33339 bytes
SHA-256: 916f15deea74d04605a1d370a2b5284bea1b8c5a7a818ff3f7f7d47255739af8
Detection
ClamAV: Doc.Dropper.Agent-6412232-1
Obfuscation or payload: unlikely
objdata_09_off000c8600.bin rtf-objdata-decoded RTF \objdata at offset 0xC8600 33339 bytes
SHA-256: e573ec0ecc3fd8e1def0a224023376ebd9aef4ef13297ce6118b8bcaa6f0e63c
Detection
ClamAV: Doc.Dropper.Agent-6412232-1
Obfuscation or payload: unlikely