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

Static analysis result for SHA-256 dab6bfa92f263814…

MALICIOUS

Office (OLE) / .DOC

201.5 KB Created: 2008-07-11 06:57:00 Authoring application: Microsoft Office Word
MD5: ae813330ee0f94833d6119e9a25e55f7 SHA-1: b0fb8427bc39eb610e87bcb391444367ac37b748 SHA-256: dab6bfa92f2638140f10370ceaa3f3e634e654def8f5d0b0f230df7a37ef8224
82 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The OLE document exhibits significant slack space and an appended payload, indicating it's a container for malicious content. While VBA macros could not be extracted due to an unsupported format, the presence of these anomalies strongly suggests a malware delivery mechanism. The exact nature of the payload and its execution method remain unclear without further analysis of the appended bytes.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 206,336 bytes but its declared streams total only 16,543 bytes — 189,793 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.
  • 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.