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

Static analysis result for SHA-256 656d3000395b2969…

MALICIOUS

Office (OLE) / .DOC

110.5 KB Created: 2008-01-09 06:03:00 Authoring application: Microsoft Word 10.0
MD5: b8b13954a0d34331d623f5a32ae867a8 SHA-1: 9f2f54dc3c339285fcc1204a845c0690340d3890 SHA-256: 656d3000395b296934e50c8432760c157e9e8994bfaea9c20de0b4d3fcd5f49d
80 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The OLE document exhibits anomalies in its structure, specifically a large slack region and appended executable-looking payload bytes. This suggests the file is designed to deliver a secondary malicious payload. No specific family could be identified from the available evidence.

Heuristics 2

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 113,152 bytes but its declared streams total only 16,536 bytes — 96,616 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.