Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 ee64931dac0ae1f1…

MALICIOUS

RTF / .DOC

96.9 KB
MD5: e1bae052d5a86db65ee38990c31e0423 SHA-1: c3f4d4d6e77b8f3d57812d0429b8af8c5fbbca5e SHA-256: ee64931dac0ae1f14004a8ad48b72bb09c7fe456e8e52015ea9fef7b69c0fde5
120 Risk Score

Malware Insights

MITRE ATT&CK
T1559.001 Component Object Model Hijacking T1059.001 PowerShell

The RTF document contains embedded OLE objects that are triggered via \objupdate, indicating an attempt to exploit OLE activation. The presence of \objdata and \objemb heuristics further supports this. While no specific script was extracted, the OLE object likely contains a payload designed to download and execute additional malicious content. The confidence is high due to the clear exploitation indicators within the RTF structure.

Heuristics 4

  • Ole10Native stream in RTF OLE object high CVE related RTF_OLE10NATIVE_STREAM
    RTF contains an embedded OLE object with an Ole10Native stream. This is a strong payload-container signal and is related to Word/OLE exploit delivery, but it is not specific enough on its own to assign a CVE.
  • \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
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0000119a.bin
979111ce6800a4d7d3ad366188947bd484906782593b3dee08b29404c5138f3b
rtf-objdata-decoded RTF \objdata at offset 0x119A 3664 bytes