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

Static analysis result for SHA-256 7fbd22f8de0d0dcf…

MALICIOUS

Office (OLE) / .DOC

323.3 KB Created: 2008-07-11 06:57:00 Authoring application: Microsoft Office Word
MD5: 031a6e6302996d0d1fc39cc3f0693f25 SHA-1: 46562a3576a340eb983bed5512c0b75a08f08810 SHA-256: 7fbd22f8de0d0dcf4e0b979cc20d67d1daa6149aeaba9a75b55600f8a58b1c55
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The OLE document exhibits a large slack region and appended executable-looking payload bytes, indicating it's a container for malicious content. While VBA macros could not be extracted, the presence of an appended payload strongly suggests a multi-stage attack. The document body is minimal and uninformative.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 331,018 bytes but its declared streams total only 16,543 bytes — 314,475 bytes (95%) 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.