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

Static analysis result for SHA-256 a16ce76a1657e465…

MALICIOUS

Office (OLE) / .DOC

104.5 KB Created: 2008-01-09 06:03:00 Authoring application: Microsoft Word 10.0
MD5: d4d6f646a5ba54020216c2d1873d8b12 SHA-1: 15480af3bc5cca2893a830585afe8006419750e7 SHA-256: a16ce76a1657e46594c7d5a3274e05979f51241bbb418a267c5a74c946466d4b
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The file is identified as malicious due to significant anomalies in its OLE structure, including a large slack region and appended executable-looking payload bytes. The VBA extraction failed, indicating a potentially obfuscated or malformed document. The presence of appended payload bytes strongly suggests this document is a container for delivering a secondary malicious payload.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 107,008 bytes but its declared streams total only 16,536 bytes — 90,472 bytes (85%) 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.
  • Unsupported Office format for VBA extraction info OFFICE_FORMAT_UNSUPPORTED
    olevba could not extract VBA macros (PermissionError); format-agnostic byte-level scans still ran. Likely legacy, encrypted, or malformed OLE/OOXML — re-scanning the same bytes will yield the same outcome.