RTF / .DOC malware analysis — malicious · 682dea22ce7181da

MALICIOUS

RTF / .DOC

233.0 KB First seen: 2022-06-24

MD5: 4a26daa274982ad8bb592faf2e0ad65f SHA-1: 2dcd8e52e0ba40803dc6c1f5bae56ad3153cbb61 SHA-256: 682dea22ce7181da5018d5a783d456a6057c0211c698b030fdfb5697ffd1923d

220 Risk Score

Malware Insights

MITRE ATT&CK

T1566.001 Spearphishing Attachment T1203 Exploitation for Client Execution

The RTF document contains OLE object data and triggers heuristics related to CVE-2017-8570, which is known to drop SCT scripts. The document body explicitly instructs the user to 'click Enable Editing when opening', indicating a lure to bypass security. The embedded OLE object data likely contains the malicious script payload.

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` `1431c784ed39c8935ac1ae44f9d45417e73829a80d200ec70b87171f7c7462c1`	rtf-objdata-decoded	RTF \objdata at offset 0x95D	23120 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 1 shell/COM execution token(s).
`objdata_01_off0000c5d5.bin` `625ba87dad062d63542a2f08013c93a4f9eac2363a88c9240f1688e698b82c02`	rtf-objdata-decoded	RTF \objdata at offset 0xC5D5	2632 bytes
`objdata_02_off0000db78.bin` `142dc43284d9abe994719f8fb67bc4c04bfc3f07528a1a66b0bad7e552ee8e78`	rtf-objdata-decoded	RTF \objdata at offset 0xDB78	12297 bytes

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