Malicious RTF — malware analysis report

Static analysis result for SHA-256 5d1f887bc73a9589…

MALICIOUS

RTF

11.5 KB
MD5: 4eee0220a24d92a4a36c944c48661c54 SHA-1: 46b21b05e6c6fe8b78b133a9765030b25469a160 SHA-256: 5d1f887bc73a9589267017bbef5f3a553fcd631750eaa10113bedf447abf3c6e
120 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains embedded OLE object data and specifically triggers heuristics for a split hex Equation Editor ProgID and objupdate, indicating exploitation of a known vulnerability in the Equation Editor component. This technique is commonly used to achieve arbitrary code execution, typically to download and run a second-stage payload. No document body or script content was available for further analysis.

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_off00001b23.bin
3c920e04269004e947d03a1639f132d33e35918128e69609ad38dd88b06f0c71
rtf-objdata-decoded RTF \objdata at offset 0x1B23 1713 bytes