Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 bd23eaf8a774996d…

MALICIOUS

RTF / .DOC

18.1 KB First seen: 2023-03-15
MD5: 74a3e24f271d862ec3ee20c576734e59 SHA-1: 3c5f69cc956a0eb58656e4e6257a5a4726d7d9bf SHA-256: bd23eaf8a774996dcd44000b92b96879a7bae538b1e7a7e5eb94c1fcc471eb53
160 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File: User Execution T1059.005 PowerShell

The sample is an RTF document that contains an embedded OLE object, specifically targeting the Equation Editor vulnerability. The document body includes a lure instructing the user to 'click Enable editing from the yellow bar above', which is a common tactic for malware droppers. The presence of the Equation Editor exploit suggests an attempt to execute arbitrary code upon user interaction.

Heuristics 5

  • 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
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • 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_off0000262e.bin
72717e49d6f795e74f9d8338bde6c16f9237688f8e19818883e6a398e235b428
rtf-objdata-decoded RTF \objdata at offset 0x262E 1956 bytes