RTF malware analysis — malicious · 599053a32664155b

MALICIOUS

RTF

704.0 KB First seen: 2019-05-31

MD5: 7a20c1ab318c1d72df526ea0cce26a5e SHA-1: bc7c71e8401963383c2278040f917dc6faf1744b SHA-256: 599053a32664155b4b52a93827139edfb782f4d8b9b5fa7f35356ccf3b6fa37c

220 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains multiple OLE objects and ".objupdate" directives, indicating it is designed to exploit vulnerabilities. Specifically, the "CVE_2017_8570" heuristic firing confirms the use of a Composite Moniker to drop an SCT script, which is a known technique for executing arbitrary code. The embedded OLE object data, particularly at offset 0xB5D2, is the likely source of this exploit.

Heuristics 6

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
Embedded OLE object medium RTF_OBJEMB

RTF contains \objemb — embedded OLE object

Extracted artifacts 5

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off00000025.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x25	336318 bytes
SHA-256: `cef155616b50120eb6383619b4c4d606495e2dc2027ef09680e185b47dff1ece`
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact entropy is 8.00, consistent with packed or encrypted content.
`objdata_01_off000ad40e.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xAD40E	1056 bytes
SHA-256: `38e0a590df7eaa9868af736886281809be3c0fe6a6a6ea4e0327baa813cb5642`
`objdata_02_off000adc8a.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xADC8A	429 bytes
SHA-256: `c861ab3ab7d28ef7b028a69afbbfc89c1f5c98f0be9f15b26f0565b7d5605703`
`objdata_03_off000ae020.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xAE020	1351 bytes
SHA-256: `fbfe6031f946bf25c25f9783662a0516de4f34007dcfe7ff53f2b540dbc1df3f`
Detection ClamAV: No threats found Obfuscation or payload: likely Static shellcode analysis recovered command string(s): cscript //nologo %vbs%
`objdata_04_off000aeb2c.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xAEB2C	2633 bytes
SHA-256: `1f8de175e345e5b9624b8bb5f76e9d4c1d78de3a7bbc2750e8ea7def36f04cfb`

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