RTF malware analysis — malicious · a4ddd9f0d3d25675

MALICIOUS

RTF

334.8 KB First seen: 2021-07-07

MD5: f07b2a43a8478a45bb4fe6b54d2cdfb1 SHA-1: 3a0165713c433becf92c0e70e4480b92fd4983d4 SHA-256: a4ddd9f0d3d25675037497e1beb9d2fbd396958caba6dd8f558f554d0f85863d

280 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF document contains multiple indicators of malicious OLE object embedding, specifically related to CVE-2017-8570. The heuristic firings indicate the presence of composite monikers and an ".objupdate" directive, suggesting the document is designed to automatically activate embedded objects. The "SE_ENABLE_LURE" heuristic further suggests the document prompts the user to enable editing, a common tactic for malware droppers. The embedded OLE object likely contains shellcode or a script designed for execution.

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	59583 bytes
SHA-256: `168eeba4352440e59196c40987144851d2ee13bd99b88240c5558e42b04f58dc`
`objdata_01_off0000735b.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x735B	59556 bytes
SHA-256: `c32e4134fc8fc4ff4c4ef101be002523de1fc6ebc75b30eb2e5ea8e79a98d31a`
Detection ClamAV: No threats found Obfuscation or payload: likely Static shellcode analysis recovered command string(s): WScript.Shell"")")
`objdata_02_off000257e0.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x257E0	2632 bytes
SHA-256: `a8e170497da15decc11753d202c99c86f7a7ffd2d52481e6b9c79a5403675379`
`objdata_03_off00026d83.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x26D83	12297 bytes
SHA-256: `e8d4fe950caed6dcfde26f4b616825bbe11b93458425974b7d075167f675abf7`

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