Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 dc6ae45c39a9f577…

MALICIOUS

RTF / .DOC

17.2 KB First seen: 2023-03-15
MD5: 6d90d5d219340cc50043acc39c1d47b1 SHA-1: 4913b747c2a5b0e83dedd3f55ed1775cad21bc02 SHA-256: dc6ae45c39a9f5777bfd1b77e7e948aac90bf0d75974b8fa25a06b612786d67a
140 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File

The file is an RTF document containing an embedded OLE object with a split Equation Editor ProgID, indicating an attempt to exploit a known vulnerability. The presence of \objupdate and the SE_ENABLE_LURE heuristic confirm that the document is designed to trick the user into enabling editing, which would then activate the embedded object and likely trigger the exploit. No scripts were extracted, and the document body content is a generic lure unrelated to the exploit.

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_off0000212a.bin
400d5a40945782dff9db8180c1c03c02d456735e87119c8af6e074acdd26cecd
rtf-objdata-decoded RTF \objdata at offset 0x212A 2032 bytes