RTF / .DOC malware analysis — malicious · 82f063e5bdf4d7bd

MALICIOUS

RTF / .DOC

233.0 KB First seen: 2022-06-21

MD5: e0e60a4c8c2ffe66978633ed90fb7bde SHA-1: 263c022e20e152a8b4a888c1a458889efe260ba7 SHA-256: 82f063e5bdf4d7bd5b23d72d7d411e0988eef0686eb5b8704958f817dc17266f

220 Risk Score

Malware Insights

MITRE ATT&CK

T1204.002 User Execution: Malicious File T1566.001 Phishing: Spearphishing Attachment T1059.005 Command and Scripting Interpreter: Visual Basic

The RTF document contains OLE object data and triggers heuristics related to CVE-2017-8570, indicating it drops a script. The document body explicitly instructs the user to 'download the document and click Enable Editing', a common lure to bypass macro security. This suggests the document's primary purpose is to exploit this vulnerability to execute a malicious script, likely for further payload delivery.

Heuristics 7

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
Macro/content-enable lure medium SE_ENABLE_LURE

Document instructs the user to enable macros or editing — a common technique used by malware droppers to bypass Office macro security settings
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_off0000095d.bin` `67177a8bf858e6a8b7f17d00eb90d76b37c89fde1f20ad5edbe0ffb8b2c9e7d3`	rtf-objdata-decoded	RTF \objdata at offset 0x95D	23116 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 1 shell/COM execution token(s).
`objdata_01_off0000c5cb.bin` `4aa0e7f5ab53bb62fd4a60818892a21fcbe35dba260d2112984f00988c699ebb`	rtf-objdata-decoded	RTF \objdata at offset 0xC5CB	2632 bytes
`objdata_02_off0000db6e.bin` `142dc43284d9abe994719f8fb67bc4c04bfc3f07528a1a66b0bad7e552ee8e78`	rtf-objdata-decoded	RTF \objdata at offset 0xDB6E	12297 bytes

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