Malicious RTF — malware analysis report

Static analysis result for SHA-256 2af5c37cecd6405e…

MALICIOUS

RTF

87.0 KB First seen: 2024-08-23
MD5: 9b11ffc668d7fde9f491c1366d298403 SHA-1: 1ac90b45512867aee829209f01cfc89b05620451 SHA-256: 2af5c37cecd6405e5217b76fe88e9b7aa109902c453a94819e91aff17d424973
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 sample is an RTF document that contains OLE object data and triggers an object update, indicating it attempts to exploit the Equation Editor vulnerability (CVE-2017-11882). This exploit is known to download and execute a secondary payload. The presence of RTF-specific heuristics strongly suggests this attack vector.

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_off00001758.bin
563548075527356361eb55aaca66c356b5594b27178aa294c5cbc5615c63b675
rtf-objdata-decoded RTF \objdata at offset 0x1758 1759 bytes