Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 026b231397a616cf…

MALICIOUS

RTF / .DOC

39.5 KB First seen: 2023-02-16
MD5: 0ae80f592fd26eab1fff0cfc1f809c4d SHA-1: 0008cd180d215664e5eb6bf7e3038f5624cbba7a SHA-256: 026b231397a616cfd92bb32327aafd4ce5584ee1c98e4c0f2f88c1888f0d8171
140 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious Link T1204.002 Malicious Link: Malicious File T1559.001 Component Object Model Hijacking

The RTF document contains embedded OLE object data and specifically triggers heuristics related to the Equation Editor vulnerability and OLE activation. The document body includes a lure instructing the user to 'Enable editing', a common tactic to bypass security measures. This suggests the file is designed to exploit the Equation Editor vulnerability to execute a secondary payload.

Heuristics 4

  • 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
  • Macro/content-enable lure medium SE_ENABLE_LURE
    Document instructs the user to enable macros or editing — a common technique used by malware droppers to bypass Office macro security settings

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00005c18.bin
74e3746b9bfc730b3a754f4da42864d31f9666edbcea911b4c40b09504c3d84e
rtf-objdata-decoded RTF \objdata at offset 0x5C18 1963 bytes