RTF malware analysis — malicious · 9b67faeed1ff38ac

MALICIOUS

RTF

334.8 KB First seen: 2021-07-07

MD5: acc28a7531ee3a329c5f27f71975b751 SHA-1: f486629f9cefdd117b62c2a743d7e62b1eda659c SHA-256: 9b67faeed1ff38ac5a56953393a435fcab6361d63c7d8a506f79b9bf73fb8b39

280 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains multiple indicators of malicious OLE object embedding, specifically triggering high-severity heuristics related to CVE-2017-8570 and composite monikers. The presence of embedded OLE objects and the ".objupdate" directive strongly suggest an attempt to execute arbitrary code. The "SE_ENABLE_LURE" heuristic indicates the document likely prompts the user to enable editing or macros, a common social engineering tactic. The extracted artifact objdata_01_off0000735b.bin is flagged as suspicious.

Heuristics 8

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.
Automatically linked OLE object high RTF_OBJAUTLINK

RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
\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.
Suspicious extracted artifact high 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.
OLE object data medium RTF_OBJDATA

RTF contains 4 \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

Extracted artifacts 4

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off00000bac.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xBAC	59591 bytes
SHA-256: `0dd51e5fd014bf68733c217b610d78c2bd22f1af825aabbc811250bcdd69ba1f`
`objdata_01_off0000735b.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x735B	59564 bytes
SHA-256: `f05da1879a05036501f205e7145a70015ed6b0c703e084cab9e0525c40094128`
Detection ClamAV: No threats found Obfuscation or payload: likely Static shellcode analysis recovered command string(s): WScript.Shell"")")
`objdata_02_off000257f0.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x257F0	2632 bytes
SHA-256: `a8e170497da15decc11753d202c99c86f7a7ffd2d52481e6b9c79a5403675379`
`objdata_03_off00026d93.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x26D93	12297 bytes
SHA-256: `e8d4fe950caed6dcfde26f4b616825bbe11b93458425974b7d075167f675abf7`

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