Malicious RTF — malware analysis report

Static analysis result for SHA-256 31f3c7130170cd16…

MALICIOUS

RTF

4.5 KB
MD5: 8bbcebb8f10e9be6d22f81fc04351334 SHA-1: e8b235368d0756d698a76b8994ce56eff1339e83 SHA-256: 31f3c7130170cd169dd97478604fe953343eee45b7745bd76ebe6f1be1af3296
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 OLE object activation. This indicates the document is designed to exploit a vulnerability in Microsoft Equation Editor, likely to achieve arbitrary code execution upon opening. No further IOCs were extracted from this sample.

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_off000000b1.bin
94818961131f5d37b86eb2d6c45b7ad33e42e2dd2b425f65b352c27ea0fb4c40		 rtf-objdata-decoded RTF \objdata at offset 0xB1 2040 bytes

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