RTF malware analysis — malicious · 757063078064634f

MALICIOUS

RTF

59.3 KB First seen: 2019-04-18

MD5: 0ef98e66d602670d004e6eaa986e9202 SHA-1: cbcb6531dfd823a898bca79b6f136f2a4e00f807 SHA-256: 757063078064634f8aed62cb66daca37578a8fb16b673168fd7bb89748efaedb

120 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains an embedded OLE object with a split Equation Editor ProgID, indicating exploitation of a known vulnerability (CVE-2017-11882). The \objupdate directive forces the activation of this object, leading to arbitrary code execution. This is a common technique for delivering secondary payloads, though no specific payload or C2 infrastructure was directly observed in this static analysis.

Heuristics 3

Split hex Equation Editor ProgID + OLE object critical CVE likely RTF_EQUATION_EDITOR

RTF embeds the Equation.3 ProgID as hex bytes near OLE object activation and splits the byte stream with whitespace or an ignorable RTF group. This is an Equation Editor OLE activation surface commonly used by CVE-2017-11882 / CVE-2018-0802 exploit documents.
\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.
OLE object data medium RTF_OBJDATA

RTF contains 1 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off000050f1.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x50F1	1458 bytes
SHA-256: `2d42a273c00b9aa736620077526e4ad34e978a102fa829781bda056cc0876675`

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