Malicious RTF — malware analysis report

Static analysis result for SHA-256 2830c2aec7bdb7e9…

MALICIOUS

RTF

111.3 KB First seen: 2023-08-15
MD5: c95a1304a0b69d9e0c099f3bc6eedcca SHA-1: 7747eec83327a902d966b82507e511b43307991b SHA-256: 2830c2aec7bdb7e9090c79d6d95b422cbe875bd5a7ec1f55fb54a9165be1e48d
140 Risk Score

Malware Insights

MITRE ATT&CK
T1204 User Execution T1204.002 Malicious File

The RTF file contains an embedded OLE object with a split Equation Editor ProgID, and an \objupdate directive that forces OLE activation. The document body includes a lure instructing the user to 'Enable editing', which is a common technique to bypass macro security settings and trigger the exploit. The presence of these elements strongly suggests an attempt to exploit a vulnerability, likely related to the Equation Editor, to execute malicious code.

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.

FilenameKindSourceSize
objdata_00_off00003834.bin
921eb70f03ca3421c4437b8294931287074069c9b2b51f36656930b707de7faf
rtf-objdata-decoded RTF \objdata at offset 0x3834 1989 bytes