RTF / .DOC malware analysis — malicious · a8920f5026243373

MALICIOUS

RTF / .DOC

477.4 KB First seen: 2023-01-26

MD5: efe233b3ffe0cc102592415257fb8a41 SHA-1: 19cde54f139b31a24e715ced3ad72c6d3a45a721 SHA-256: a8920f5026243373c34756d2332a35b691ef70d15a6edf82a95a934cd1eaa2df

200 Risk Score

Malware Insights

MITRE ATT&CK

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

The sample is an RTF document that leverages OLE object data and a composite moniker to exploit CVE-2017-8570. This vulnerability allows for the execution of arbitrary code, typically used to download and run a secondary payload. The document body appears to be a fake invoice, likely a lure to trick the user into opening the malicious content.

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_off000378b4.bin` `af541bc38a4391f86a9047308bd2ace4fcc307b87dca9d9f080c4c61468249b2`	rtf-objdata-decoded	RTF \objdata at offset 0x378B4	35192 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 1 shell/COM execution token(s).
`objdata_01_off00049740.bin` `24fedef2d4fe5e3d6666fae2543850c54134511ad6be8583d5aa0438ef699c5d`	rtf-objdata-decoded	RTF \objdata at offset 0x49740	2632 bytes
`objdata_02_off0004ace3.bin` `142dc43284d9abe994719f8fb67bc4c04bfc3f07528a1a66b0bad7e552ee8e78`	rtf-objdata-decoded	RTF \objdata at offset 0x4ACE3	12297 bytes

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