Malicious RTF — malware analysis report

Static analysis result for SHA-256 5dc526e3480878e9…

MALICIOUS

RTF

92.9 KB First seen: 2024-08-06
MD5: 515c7e4dae4099ca2e13a4055a1a5321 SHA-1: de03b5ecc5d6898264066de4f06a83075641fc95 SHA-256: 5dc526e3480878e95e87930df352e9dab0c3f3bba9d48edb3e0a9b7d1cad362c
140 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious Link T1059 Command and Scripting Interpreter T1566 Phishing

The sample is an RTF document that contains an embedded OLE object, specifically targeting the Equation Editor vulnerability. The presence of \objupdate indicates that the OLE object is designed to be activated automatically, likely triggering the execution of a secondary payload. The extracted objdata suggests the presence of executable content.

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
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00001126.bin
6d780cfc929dd92d18f392d5c482f643716747c93e26e51938d2f58ebe9a483c		 rtf-objdata-decoded RTF \objdata at offset 0x1126 1948 bytes

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