Malicious RTF — malware analysis report

Static analysis result for SHA-256 6d4ae87c16a062e0…

MALICIOUS

RTF

28.9 KB First seen: 2019-12-10
MD5: fcdb2fc48eabb82a3ca6f15433d285df SHA-1: 5e4871b55e173e913b635a3aa9e1fa44ae169645 SHA-256: 6d4ae87c16a062e027f1bd3cf7ec68e00bf2fb1965be84e08eb87bcf12ce5ea6
120 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The RTF file contains an embedded OLE object with a split Equation Editor ProgID, indicating an attempt to exploit a known vulnerability. The \objupdate directive forces the activation of this object, leading to arbitrary code execution. No specific family could be identified from the available evidence.

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_off00005c5c.bin rtf-objdata-decoded RTF \objdata at offset 0x5C5C 1412 bytes
SHA-256: 9bf17a298762266308aa32f9e9ffe65a39a983bdb39b52a76b114a4fbf2b259e