Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 e8b2cdf9e9676f57…

MALICIOUS

RTF / .DOC

390.4 KB Created: 2022-09-15 First seen: 2022-09-21
MD5: 0fd7f9024fa8f517377567506e46ee7d SHA-1: 08e14fc1f09547e4619117528882797474ad68e4 SHA-256: e8b2cdf9e9676f57b754986984d914d96d5ee259c9e037e155301112e594f6ef
262 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious Link T1204.002 Malicious Link: Malicious File T1059 Command and Scripting Interpreter T1566 Phishing T1566.001 Phishing: Spearphishing Attachment

The file is an RTF document that leverages multiple critical vulnerabilities (CVE-2017-8570 and CVE-2017-8759) related to OLE object activation. The heuristics indicate the embedding and activation of OLE objects, specifically mentioning Composite Moniker and MSXML SAX OLE activation, which are known vectors for exploiting these CVEs. This strongly suggests the document is designed to drop and execute a malicious script or payload.

Heuristics 8

  • Composite Moniker — CVE-2017-8570 (drops SCT script) critical CVE related CVE_2017_8570
    RTF \objdata decodes to OLE data containing the Composite Moniker — CVE-2017-8570 (drops SCT script) CLSID — the vulnerable control/moniker is embedded directly in the document's object stream, the delivery shape of this exploit. RTF objects auto-render when Word opens the file.
  • 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.
  • Composite Moniker in RTF OLE object high CVE related RTF_COMPOSITE_MONIKER_RELATED
    RTF contains Composite Moniker CLSID in OLE object context, but no nearby scriptlet/SCT payload was confirmed. Treat as related moniker attack-surface evidence rather than proof of CVE-2017-8570 exploitation.
  • \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 3 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • Suspicious extracted artifact medium EXTRACTED_FILE_STATIC_TRIAGE
    One or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.
  • 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.microsoft.com/office/word/2003/wordml

Extracted artifacts 3

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0000e144.bin
ec0a46789d30442d7159efcc1be3475797a14a86d0d79c5e6f4b1a63c0ba72aa
rtf-objdata-decoded RTF \objdata at offset 0xE144 74049 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 1 shell/COM execution token(s).
objdata_01_off00033b88.bin
43dc420203828d24ec36adf809a9ada54bc1f182c6dd7bd39e852b7059bf1a1d
rtf-objdata-decoded RTF \objdata at offset 0x33B88 2632 bytes
objdata_02_off0003512b.bin
142dc43284d9abe994719f8fb67bc4c04bfc3f07528a1a66b0bad7e552ee8e78
rtf-objdata-decoded RTF \objdata at offset 0x3512B 12297 bytes