Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 ed90e45ef1148b15…

MALICIOUS

RTF / .DOC

65.8 KB First seen: 2023-09-22
MD5: 51b0e533b975392310347afa66dd6a68 SHA-1: e72a22bcaf8dcd4ed8d7066fcd7a6f7d66df01ee SHA-256: ed90e45ef1148b15f2fd2973dcc9d683b521e7ff4fe6874033772dbcb638641c
140 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious Link T1204.002 Malicious Link: Malicious File T1059 Command and Scripting Interpreter T1059.005 Command and Scripting Interpreter: Visual Basic

The sample is an RTF document containing an OLE object and an Equation Editor exploit. The heuristic 'SE_ENABLE_LURE' indicates the document likely contains a prompt to 'Enable editing' to bypass security measures. This suggests the document is designed to exploit a vulnerability, likely CVE-2017-11882, to download and 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_off00003cd7.bin
ddfb1c406313bdd0ac62c6b3e6d46916a394518e7f56d69175d79a6f224efcb1
rtf-objdata-decoded RTF \objdata at offset 0x3CD7 1493 bytes