Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 6ea18978fb71fe68…

MALICIOUS

RTF / .DOC

147.1 KB
MD5: 428f467bcc5858d19804cbd26b6ed599 SHA-1: 11557ed0903701b405f29d21e46cfe2495e0fce6 SHA-256: 6ea18978fb71fe6885f82e191911f7057ea8a5c6470a6ca93f2c12832a5c451c
100 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF document contains OLE object data that is forced to activate via \objupdate, indicating an attempt to execute embedded content. The presence of \objupdate and Ole10Native stream strongly suggests exploitation for client execution. While no specific family is identified, the technique points towards a malicious document used as an initial attack vector.

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_off000011c4.bin
962e937a2c65a1512d33d77edaf3c44891c52b28f14b6cb2f517218951fbec7b
rtf-objdata-decoded RTF \objdata at offset 0x11C4 4199 bytes