Malicious RTF — malware analysis report

Static analysis result for SHA-256 4b1da5728b996ab7…

MALICIOUS

RTF

21.6 KB First seen: 2020-07-02
MD5: 0764987696f1c998f26e3934852a4b89 SHA-1: 727f0f510bdf647fcfce152daeaa44a0c6b1a3d3 SHA-256: 4b1da5728b996ab79cb7b1a354473fdd36d9c3db938097183f6f4595ddab608f
120 Risk Score

Malware Insights

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

The RTF file contains OLE object data and specifically triggers heuristics for Equation Editor exploitation and OLE object activation. This indicates the file is designed to exploit a vulnerability, likely CVE-2017-11882, to execute code. The embedded OLE object, decoded as objdata_00_off00001e3b.bin, is the likely payload delivery mechanism. No specific family could be identified.

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_off00001e3b.bin rtf-objdata-decoded RTF \objdata at offset 0x1E3B 1476 bytes
SHA-256: 4f2d944aca3426c5adc3b7e0b251913333c3d56c4718b592add43c0e6442a55e