RTF malware analysis — malicious · 67f7dfabd4c2382f

MALICIOUS

RTF

1.14 MB First seen: 2019-03-18

MD5: 2d5d16dab075a9aa18d7f6ee35f5b955 SHA-1: 57ed5c5c6634efd64b1a721ae08d358cfa9d6516 SHA-256: 67f7dfabd4c2382fe8596a746bb5b9fbc824d40f7394d6507fa550bbfa56b5b3

222 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution

The RTF file contains multiple indicators of exploitation for CVE-2017-8570, including the presence of Composite Monikers and OLE object data. This vulnerability is known to be used for dropping and executing script files, likely to download and run a second-stage payload. The excessive hex data within OLE objects suggests a hidden 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.
Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX

RTF contains ~1181KB of hex-encoded data inside \objdata sections — may hide a payload
OLE object data medium RTF_OBJDATA

RTF contains 7 \objdata section(s) — embedded OLE objects
Embedded OLE object medium RTF_OBJEMB

RTF contains \objemb — embedded OLE object
Suspicious extracted artifact info 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 7

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off00000025.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x25	205 bytes
SHA-256: `75a725fc96463ea024899f12597b26031b1a5d84ddd2de407d47914073b3db59`
`objdata_01_off000001ee.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x1EE	385227 bytes
SHA-256: `8f59e65595946fceac4e31edc509b0ce12abb8ca5a6869e54e0a55ca2ae3f3eb`
`objdata_02_off000ee371.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xEE371	1068 bytes
SHA-256: `2b28d78ceb2a564ae30f2b6865926b068f3f920a373c2e3fc4cb865091eddd89`
`objdata_03_off000eec02.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xEEC02	102092 bytes
SHA-256: `5db94c0d048eb070c49e1975e64a966ed4ef4d812521929e6e1e051621300c46`
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact entropy is 7.48, consistent with packed or encrypted content.
`objdata_04_off001209d2.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x1209D2	369 bytes
SHA-256: `3c0b4878e98d51d984a06b9ba36e54869ecd67e41f335730fced4ca28976d877`
`objdata_05_off00120cf0.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x120CF0	890 bytes
SHA-256: `21dcdf875b1972c61c0e8c2c2123f9a95c8f29fb4a2cf8bf52511b328881de8e`
`objdata_06_off00121462.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x121462	2633 bytes
SHA-256: `27c6d10cfe7974ebf40c1200cc005f9878cc37b7d49ece9cbc396d700c38918a`

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