RTF / .DOC malware analysis — malicious · af77d06fef657894

MALICIOUS

RTF / .DOC

223.7 KB First seen: 2022-08-11

MD5: 8760b2a1996ff5fe0059907170329174 SHA-1: ea548b731c416a0128fb3fc663e21c0f1126954d SHA-256: af77d06fef657894e3e393ccc8297d0ec279b7f7e23a4954b630ceb67feaec88

200 Risk Score

Malware Insights

MITRE ATT&CK

T1204 Malicious Link T1204.002 Malicious Link: Malicious File T1059 Command and Scripting Interpreter T1059.003 Command and Scripting Interpreter: Windows Command Shell

The RTF file contains embedded OLE objects, specifically triggering the CVE-2017-8570 vulnerability. This vulnerability is known to be used for dropping and executing script files, indicated by the 'objdata_00_off000007d2.bin' artifact. The composite moniker further supports the exploitation of this vulnerability to achieve arbitrary code execution.

Heuristics 6

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

Extracted artifacts 3

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off000007d2.bin` `6019eeaefdcea156a69f83bb3833f2828968df4519ce8cb2cd7f3ddd40e75373`	rtf-objdata-decoded	RTF \objdata at offset 0x7D2	18758 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 1 shell/COM execution token(s).
`objdata_01_off0000a0d8.bin` `3c97121fe02f90da16cb2983b3ae893ea40de52f15d26984fbdbae19aab20ebc`	rtf-objdata-decoded	RTF \objdata at offset 0xA0D8	2632 bytes
`objdata_02_off0000b67b.bin` `142dc43284d9abe994719f8fb67bc4c04bfc3f07528a1a66b0bad7e552ee8e78`	rtf-objdata-decoded	RTF \objdata at offset 0xB67B	12297 bytes

Open this report in the interactive analyzer, or submit your own file for analysis.