Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 e434cb0b93828067…

MALICIOUS

RTF / .DOC

64.4 KB
MD5: f9129e0d5b35a3a13083630a2f6998d5 SHA-1: 3615dc2be91b022c8da2bc0d637c4e5341456ab1 SHA-256: e434cb0b938280676e9ac04f72da8212b8ea1e4a3692c24c2d5e5f606a96910e
100 Risk Score

Malware Insights

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

The sample is an RTF document exhibiting high-severity heuristics for OLE object data, automatic linking, and forced updates. These indicate the document is designed to exploit vulnerabilities related to embedded OLE objects, likely to trigger the execution of a secondary payload. No document body or script content was available for further analysis, limiting the ability to determine the exact nature of the payload or its specific family. The confidence is moderate due to the lack of explicit payload details.

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

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000008f1.bin
25f9ca5bbaab105d597bbb022a55b1cee515ee6bd114600fd0335349dd277e08
rtf-objdata-decoded RTF \objdata at offset 0x8F1 3668 bytes