Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 be808db4267948cb…

MALICIOUS

RTF / .DOC

5.8 KB
MD5: acf18a49dc4dca6ff87631a8c7c52916 SHA-1: 3a4c4c398a2eb92f16b7ddfca634cc2672f08441 SHA-256: be808db4267948cbc699da12dffa6b6897187244d71ab00e4c2f7ec53128a698
160 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File T1059.003 Windows Command Shell

The RTF document contains OLE objects and specifically triggers the RTF_EQUATION_EDITOR heuristic, indicating exploitation of the Equation Editor vulnerability. The presence of objupdate and objautlink suggests automatic activation of the embedded OLE object, which is a common method for delivering malicious payloads. No document body text or scripts were provided, so the exact payload and delivery mechanism beyond the exploit itself cannot be determined.

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.
  • 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 2 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000006c9.bin
e6121f82224f02fa13a20f518724be3d69f030ffa7c184431af89d01f73ec40f
rtf-objdata-decoded RTF \objdata at offset 0x6C9 1488 bytes