Malicious RTF — malware analysis report

Static analysis result for SHA-256 30b948a3c93cf7e9…

MALICIOUS

RTF

83.5 KB First seen: 2024-08-13
MD5: 36e32dbcca3f5c62542f9b67b7f3de77 SHA-1: 0b9bfeb337aadce0a6920f13b5fdfbc3c52b952d SHA-256: 30b948a3c93cf7e961e828766eb57fe98c0154a293ffa6b32721ff486fc392cf
120 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious Link T1566.001 Spearphishing Attachment

The RTF file contains embedded OLE object data and triggers an ".objupdate" command, indicating an attempt to exploit the Equation Editor vulnerability. This technique is commonly used to download and execute a second-stage payload, likely leading to further system compromise.

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_off00000df6.bin
62ef3ef0bf12a6242868afe984ff36a4ae6f39c1b261635ed5a4c293f53937ac
rtf-objdata-decoded RTF \objdata at offset 0xDF6 1802 bytes