Malicious RTF — malware analysis report

Static analysis result for SHA-256 f7e1c9c8677c1aed…

MALICIOUS

RTF

32.4 KB
MD5: 077fe021629cf27c561498671a2e112d SHA-1: 47d5c5b72b2061d29ae65ed9c3c9913733ef4408 SHA-256: f7e1c9c8677c1aed7f4f80728a943178730b46844b4571b313b10a0c61bc354c
120 Risk Score

Malware Insights

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

The file is an RTF document containing OLE object data and specifically triggers heuristics for the Equation Editor vulnerability and OLE object activation. This indicates a likely exploitation attempt to gain code execution. The presence of ".bin [rtf-objdata-decoded] 1621 bytes" suggests a dropped or embedded component, which is commonly used to download and execute further stages of malware.

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 2 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0000109e.bin
2c4e3003d6ab2bc3b941a0ab3aab38e09901ad3c45c6cf52e0122255a1e1b1a2
rtf-objdata-decoded RTF \objdata at offset 0x109E 1621 bytes