Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 c2d3f8d87feaec6e…

MALICIOUS

RTF / .DOC

25.9 KB First seen: 2022-11-23
MD5: 3f6c7ad16cf47199a9dfbe2944554ef4 SHA-1: eae5ac08cc4cb0da9561dde7e64d323e83b20f7b SHA-256: c2d3f8d87feaec6e82fbce209dd28929b7567ba62713522dd9b0d149b09993a7
140 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious Link T1059.005 Visual Basic

The sample is an RTF document containing an embedded OLE object, specifically leveraging the Equation Editor vulnerability. The 'SE_ENABLE_LURE' heuristic indicates the document prompts the user to enable editing, which is a common tactic for malware droppers to bypass security measures and trigger the exploit. The embedded OLE object data is the primary indicator of compromise.

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_off00004c75.bin
41ac38eb6f531cad50a5952c6a238d818ef46fda95e8c36d4e3356f374b8ee61
rtf-objdata-decoded RTF \objdata at offset 0x4C75 1539 bytes