Malicious Office (OLE) / .DOC — malware analysis report

Static analysis result for SHA-256 01601dae62a64904…

MALICIOUS

Office (OLE) / .DOC

85.2 KB
MD5: 87cf2dbf6e726e26a6a55ddef5dc7ea0 SHA-1: 54c6326df47069a07ce4b5fee29114f7e8cc580a SHA-256: 01601dae62a64904ba93065ddacd85cf1ecc7b7d6b16d8893704919da8644a4f
80 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1027 Obfuscated Files or Information

The OLE document exhibits a large slack space and an appended executable payload, indicating it's designed to deliver a secondary malicious component. The presence of appended executable bytes strongly suggests a dropper functionality, likely delivered via spearphishing.

Heuristics 2

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 87,296 bytes but its declared streams total only 12,338 bytes — 74,958 bytes (86%) live in unallocated sector slack. This is the canonical hiding place for pre-macro-era Office exploit payloads (XOR-encoded shellcode reached via a parser pointer-corruption bug in the document structure).
  • OLE file has appended executable-looking payload bytes high OLE_APPENDED_PAYLOAD
    OLE compound file contains a large high-entropy region beyond the declared major streams and that region includes shellcode, PE, or loader API markers. This is a payload-carrier signal, not a specific CVE attribution by itself.