RTF malware analysis — malicious · d322a24b69ec5df8

MALICIOUS

RTF

40.9 KB First seen: 2023-07-11

MD5: 6222db4b607866f0fda126899cc1d293 SHA-1: 0f22f658a590ccdc9d2dcd7f26a2740e44a9fe50 SHA-256: d322a24b69ec5df8d25bd1ebd701bd738684fb2e3077852bf31afcaefec1192b

140 Risk Score

Malware Insights

MITRE ATT&CK

T1566.001 Spearphishing Attachment T1204.002 Malicious File

The RTF file contains an embedded OLE object with a split hex Equation Editor ProgID, indicating an attempt to exploit a known vulnerability. The \objupdate directive forces OLE activation, and the document body includes a lure to 'Enable editing', suggesting the file is designed to exploit the Equation Editor vulnerability upon user interaction. No scripts were extracted, and the family is unknown.

Heuristics 4

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
Macro/content-enable lure medium SE_ENABLE_LURE

Document instructs the user to enable macros or editing — a common technique used by malware droppers to bypass Office macro security settings

Extracted artifacts 1

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off000051e4.bin` `c4ff5d2393b50638c88ded3e307bdcfe213c43bd8decaa2522747ece15373a93`	rtf-objdata-decoded	RTF \objdata at offset 0x51E4	1657 bytes

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