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

Static analysis result for SHA-256 72e1de105e8573b2…

MALICIOUS

Office (OLE) / .DOC

146.4 KB
MD5: 551a648d37cbc633706c80adb95a1b79 SHA-1: 355209f05ef2a7b8c718ecf2f70d487e74a7fa1b SHA-256: 72e1de105e8573b29c5afe9fb29b61b249d793e22a53b4d705464582ab8b99b4
80 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The OLE document exhibits a high degree of slack space and contains appended executable payload bytes, indicating it is likely a dropper. The appended payload suggests the file is designed to deliver a secondary malicious component. The document body is minimal and does not provide further context on the lure.

Heuristics 2

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 149,957 bytes but its declared streams total only 12,447 bytes — 137,510 bytes (92%) 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.