Malicious RTF — malware analysis report

Static analysis result for SHA-256 17ee366ac90069ce…

MALICIOUS

RTF

76.3 KB First seen: 2024-10-08
MD5: 7a6ed8a97ecfa26cfa0d2d7eb3fae5f9 SHA-1: a80685947466f96c75f3f7927881ca7d70047b86 SHA-256: 17ee366ac90069cef2e031d80bbd9898173bc46d746bb39886555f2ddc55379c
120 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File

The RTF file contains embedded OLE object data and specifically triggers an Equation Editor exploit. The \objupdate heuristic indicates that the embedded object is designed to be activated automatically, which is a common technique for exploiting vulnerabilities like the Equation Editor flaw. This strongly suggests the file is a dropper intended to execute a secondary payload.

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.

FilenameKindSourceSize
objdata_00_off00002069.bin
6970d73c2362ceb74df94e528edbbb8fb3a85c84456b9b38ee974de743c39b16
rtf-objdata-decoded RTF \objdata at offset 0x2069 1637 bytes