Malicious RTF — malware analysis report

Static analysis result for SHA-256 79907a78826fe9e2…

MALICIOUS

RTF

306.1 KB First seen: 2019-05-10
MD5: a698aa44c6651a996b02cbe06853318b SHA-1: bcf66edeaecc00992c5288f29b19549047c93c32 SHA-256: 79907a78826fe9e24d06f0f80e3d0f9fbe2fee7855f3fd688e8c6a8cf8275a0c
120 Risk Score

Malware Insights

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

The RTF file contains an embedded OLE object and triggers heuristics related to the Equation Editor vulnerability. This indicates the file is designed to exploit a known vulnerability in the Equation Editor component to achieve code execution upon opening. The presence of ".objupdate" further suggests an attempt to force OLE object activation.

Heuristics 3

  • Split hex Equation Editor ProgID + OLE object critical CVE likely 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_off00000297.bin rtf-objdata-decoded RTF \objdata at offset 0x297 96040 bytes
SHA-256: dc8e6a64c6df2bd8171b2f9c22c4714f8c35cb2157c0756f81553e2e9f38e519

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