Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 f5ec49a46ce3250a…

MALICIOUS

RTF / .DOC

31.0 KB
MD5: d4acf465341a32fb6aa5743a75957148 SHA-1: f9e1c6c655fa31e6653997f818a88282e918fb1a SHA-256: f5ec49a46ce3250a7c89ff0c24c2a32645e1a1cf58266252b850e5b675af8b1e
100 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File T1059.001 PowerShell

The RTF document contains OLE object data and uses \objupdate to force OLE activation, indicating a likely exploit attempt. The presence of Ole10Native stream further supports this. While no specific document body content or scripts were available for analysis, these heuristics strongly suggest the file is designed to execute embedded malicious content, likely leading to a second-stage payload download or execution.

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

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00001ea3.bin
90ed7f8259769fe30284c616a01494284c206ada7f1b64c707deb585b5728da9
rtf-objdata-decoded RTF \objdata at offset 0x1EA3 3636 bytes