Malicious RTF — malware analysis report

Static analysis result for SHA-256 771abb2dd9d45565…

MALICIOUS

RTF

102.5 KB First seen: 2024-08-13
MD5: 14063e76ac284744cb2ba86de57b9072 SHA-1: a7ea877406729bac83e279d20b85c33e3a88de63 SHA-256: 771abb2dd9d45565687b372c7049a18779b3f4de35b216709eb3aae06f360561
120 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File

The sample is an RTF document containing an embedded OLE object with a suspicious Equation Editor ProgID, triggering critical heuristics for Equation Editor exploitation. The \objupdate directive indicates an attempt to force OLE activation, suggesting the file is designed to exploit this vulnerability to execute code. This is a common delivery mechanism for 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 1 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00001648.bin
3521c3ee026b1b221c4dc1bcbf5746c3b11456941e09239a25cea0293259c779
rtf-objdata-decoded RTF \objdata at offset 0x1648 2140 bytes