RTF / .DOC malware analysis — malicious · b0626686eb6079bf

MALICIOUS

RTF / .DOC

237.8 KB First seen: 2022-10-14

MD5: d0d1d0382136f841791c965323607f17 SHA-1: 78428f0e7aefeccc012d5e3381399d1eedb3f698 SHA-256: b0626686eb6079bf3f1135db25296fe365d334210d172cd8b0b37e865701bdd7

220 Risk Score

Malware Insights

MITRE ATT&CK

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

The sample is an RTF document that exploits CVE-2017-8570 via a composite moniker to drop a script. The document body contains a lure instructing the user to 'click Enable Editing when opening' to bypass security measures. This indicates a likely macro-based delivery mechanism for 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_off00000960.bin` `4c71294dab40cf38f432bf657eb28c95635e688c57fdca187a436a698654e58a`	rtf-objdata-decoded	RTF \objdata at offset 0x960	25494 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 1 shell/COM execution token(s).
`objdata_01_off0000d922.bin` `a8067f2f56086529114ca9573b5fb18bafa4bc65f99c3187b2d852749c9861bb`	rtf-objdata-decoded	RTF \objdata at offset 0xD922	2632 bytes
`objdata_02_off0000eec5.bin` `142dc43284d9abe994719f8fb67bc4c04bfc3f07528a1a66b0bad7e552ee8e78`	rtf-objdata-decoded	RTF \objdata at offset 0xEEC5	12297 bytes

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