Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 2a761f68fac6401a…

MALICIOUS

RTF / .DOC

25.6 KB First seen: 2023-07-05
MD5: 4d98203c37e8fba0c5cfc1192d1e0abc SHA-1: 4db7661e4fd1110c56838f70378cc067d34952d3 SHA-256: 2a761f68fac6401a2f1546b78fbaf1915c9ff5893ae40e88ad5f3f11300de8ea
180 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File T1059.005 Visual Basic

The RTF document contains an embedded OLE object with a split Equation Editor ProgID, a known exploit vector. The 'SE_ENABLE_LURE' heuristic indicates the document likely prompts the user to enable content, facilitating the exploitation. The primary goal appears to be the execution of a secondary payload, though no specific download URL or script was extracted.

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.
  • Automatically linked OLE object high RTF_OBJAUTLINK
    RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
  • \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_off000041cf.bin
be1d9fba7dd2c391e9c5138bb0e1231f6f981b3afc82f8868cbe993df85b6a30
rtf-objdata-decoded RTF \objdata at offset 0x41CF 1532 bytes