RTF malware analysis — malicious · 758275ba328e9dfe

MALICIOUS

RTF

4.6 KB First seen: 2019-02-10

MD5: b1e597324bb1eca064b7795468d95bd0 SHA-1: 3e0c7ab0599274defbd010f87b29941d108fc841 SHA-256: 758275ba328e9dfe24b930326579cf60aa481c53cd68d3ae2db5cc72bae66754

120 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains embedded OLE object data and specifically targets the Equation Editor, indicating an exploitation attempt. The ".objupdate" directive forces the activation of this embedded object, which is a known method for exploiting vulnerabilities like CVE-2017-11882. This technique is commonly used to achieve arbitrary code execution, likely to download and run a secondary payload.

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_off0000003c.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x3C	2324 bytes
SHA-256: `6b0be2e14b5ce43c97a21061ab2c09a36c2372095245454c7dbc0781ab9228bf`

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