RTF malware analysis — malicious · 0e2a517cffefcc88

MALICIOUS

RTF

719.6 KB First seen: 2019-11-20

MD5: aa590a773eb2297f2d474d11792f6311 SHA-1: 389c2bcc7e2e51ffd636bcd2e99e65c16ddcb669 SHA-256: 0e2a517cffefcc887ee12e07a38c8cd0386f4aa4872d61a7519b696441ae3c40

200 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains multiple indicators of malicious activity, including OLE object data and composite moniker structures. Specifically, the CVE-2017-8570 heuristic firing indicates the file is designed to drop a script, likely for execution. This points to an exploitation attempt for client execution, often delivered via spearphishing attachments.

Heuristics 5

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.
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 5 \objdata section(s) — embedded OLE objects

Extracted artifacts 5

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off00009b86.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x9B86	342841 bytes
SHA-256: `93b9aa2f1efcb40e75bb11572bda649690f8308b45cee3b01061335e18136d80`
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact entropy is 8.00, consistent with packed or encrypted content.
`objdata_01_off000b1239.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xB1239	444 bytes
SHA-256: `9a92e9b52588416922da9ff504d0e13de10f7c9209a209170102cf83da970296`
`objdata_02_off000b15e8.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xB15E8	1245 bytes
SHA-256: `2703dc2ca3c0d9e8edd5a157bc15cef46ae50607824244b9311f26196efc1de5`
Detection ClamAV: No threats found Obfuscation or payload: likely Static shellcode analysis recovered command string(s): cscript //nologo %vbs%
`objdata_03_off000b1fd8.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xB1FD8	1176 bytes
SHA-256: `c91ac4309ef02ab36f9a4c860a24ebb3013fe4a77681c323e7a8f5c6e12599bb`
`objdata_04_off000b2977.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xB2977	2633 bytes
SHA-256: `110f8b084aa55e8e8877c64f42c53df5b8dcc681ca92d57dd515ef11f616fae6`

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