RTF / .DOC malware analysis — malicious · 5c3858beb9c777c9

MALICIOUS

RTF / .DOC

218.3 KB First seen: 2022-04-11

MD5: 68ce8d55834cdac9dbca5456884ad1e7 SHA-1: f8304ee3810b047d088f3f612611d3891f9a32c2 SHA-256: 5c3858beb9c777c928c76cbe0097dd1933a68e8f42299316e6454eab5819b9ab

220 Risk Score

Malware Insights

MITRE ATT&CK

T1566.001 Spearphishing Attachment T1203 Exploitation for Client Execution

The RTF document contains multiple indicators of exploitation, including the use of Composite Monikers and OLE object data, strongly suggesting it leverages CVE-2017-8570. The document also contains a lure instructing the user to 'Enable Editing', a common tactic to bypass macro security and trigger the exploit. The embedded OLE objects and decoded objdata point to the execution of a script, likely a second-stage 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_off00000ba4.bin` `655406f6a753ff6309f3bb60d8cfc45556cec16ede55dda52a0eae19b4f39a12`	rtf-objdata-decoded	RTF \objdata at offset 0xBA4	15635 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 1 shell/COM execution token(s).
`objdata_01_off00008b4a.bin` `64b1f15a0e9494bf93ea2a1e9ea1b7d807d3f377db217eed0f95ae662942e168`	rtf-objdata-decoded	RTF \objdata at offset 0x8B4A	2632 bytes
`objdata_02_off0000a0ed.bin` `44deae4627fee3c44f54d5bd10477ec2e17f4c08135f08e2417832e36d10d037`	rtf-objdata-decoded	RTF \objdata at offset 0xA0ED	12297 bytes

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