Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 536cf2655cd38ee1…

MALICIOUS

RTF / .DOC

16.0 KB
MD5: c94c57f7093fbee0ff383406b0eddbb5 SHA-1: 45c9eceb0d9f99209ca5594618b21077e39b9026 SHA-256: 536cf2655cd38ee185fa13a7ca047e17fdacf8fa46264e44167899ef2f2fdd6c
100 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Phishing: Spearphishing Attachment T1059.001 Command and Scripting Interpreter: PowerShell T1204.002 Malicious File Execution: User Execution

The sample is an RTF document that contains OLE object data and is configured to automatically update and activate these objects. This indicates a likely attempt to exploit vulnerabilities in RTF parsing or OLE object handling to execute embedded code. While no specific script or URL was extracted, the heuristic firings strongly suggest a malicious intent to leverage OLE automation for payload delivery. The lack of readable document body text or scripts limits further analysis of the specific lure or payload mechanism.

Heuristics 3

  • 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_off00001670.bin
aa61a21a3cbd40676598345f3d8d23b552292a59d46b741efecee28da5ab8326
rtf-objdata-decoded RTF \objdata at offset 0x1670 2065 bytes