RTF malware analysis — malicious · 60cb5c4af9026c61

MALICIOUS

RTF

12.9 KB First seen: 2023-02-24

MD5: e151602a9a8dd0acd98afe92f9bdf858 SHA-1: a6a603e0ca40732917fab1d274c95ee82df5d295 SHA-256: 60cb5c4af9026c61ab0e35e184d61a593179af0bc0fbdf51eaeeacb160e2c2b5

120 Risk Score

Malware Insights

MITRE ATT&CK

T1566.001 Spearphishing Attachment T1204.001 User Execution: Malicious Link T1204.002 User Execution: Malicious File

The RTF file contains an embedded OLE object with a specific ProgID pointing to the Equation Editor, a known vector for exploiting CVE-2017-11882. The \objupdate directive further indicates that the embedded object is intended to be activated, leading to code execution. The presence of objdata suggests a secondary payload is likely embedded or fetched.

Heuristics 3

Split hex Equation Editor ProgID + OLE object critical 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_off00000e07.bin` `4a33be4e9cee699fb0f64d8150972ab65baa005fa5ab2e15fb493a4961a97050`	rtf-objdata-decoded	RTF \objdata at offset 0xE07	2110 bytes

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