Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 5f86f321ec714d97…

MALICIOUS

RTF / .DOC

241.3 KB First seen: 2023-03-25
MD5: b2e33303938d9a36cb52d3e10a7cf6ff SHA-1: b2ae72e1d379cb75f8c67f85b390934ecffffe20 SHA-256: 5f86f321ec714d973542a7eed90eae5973fa9d065faf40f56f53263ae3a5cfa1
180 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 RTF document contains embedded OLE objects with composite monikers, indicative of the CVE-2017-8570 vulnerability. This vulnerability allows the document to drop and execute a script, likely a second-stage payload. The presence of multiple OLE object data sections and the use of ".objupdate" further support this attack vector.

Heuristics 5

  • 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.
  • 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

Extracted artifacts 3

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000007d4.bin
d3720e63085df586489d8883b324adf604dea01b0f8a88580fe57fd39a98e2c4
rtf-objdata-decoded RTF \objdata at offset 0x7D4 27403 bytes
objdata_01_off0000e718.bin
a6611d501e579ac96404a9c19f7f70ee1bd26c5f4967cc103af51e1fde90fca8
rtf-objdata-decoded RTF \objdata at offset 0xE718 2632 bytes
objdata_02_off0000fcbb.bin
142dc43284d9abe994719f8fb67bc4c04bfc3f07528a1a66b0bad7e552ee8e78
rtf-objdata-decoded RTF \objdata at offset 0xFCBB 12297 bytes