Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 a57aef46ec255ab1…

MALICIOUS

RTF / .DOC

128.6 KB First seen: 2025-03-20
MD5: 7ac028158d3b52f5a3de282ac70e7367 SHA-1: e72bc9c74d495c1bbcc53e4f6e4ed4bbbda032a6 SHA-256: a57aef46ec255ab1fb6f34f26dd5e464b0b7c9fbb8550b9b78b6ad591ea31c37
100 Risk Score

Malware Insights

MITRE ATT&CK
T1566.002 Spearphishing Attachment

The sample is an RTF document containing embedded OLE object data, triggered by \objupdate directives. This indicates an attempt to execute embedded content, likely a malicious payload, upon opening. No specific family could be identified, and the document body was heavily obfuscated and unreadable.

Heuristics 3

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

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00001457.bin
4cfff6df36e91e8a3838d98de9915f770d4cb55e47319f34768295d29d1bd632
rtf-objdata-decoded RTF \objdata at offset 0x1457 3686 bytes