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

Static analysis result for SHA-256 8cc3b171ab7898c6…

MALICIOUS

Office (OLE) / .DOC

78.0 KB Created: 2008-07-11 06:57:00 Authoring application: Microsoft Office Word
MD5: 32f3b132d90085b0a49b257be79dc99a SHA-1: a46fe0bb10375224d72fc5b22949adcf9ad7cba9 SHA-256: 8cc3b171ab7898c60b0e15e733dcbcad59a31b70c46285eff5535144b919af8a
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The file is an OLE document with a significant amount of appended executable-looking payload bytes, indicating it's likely a dropper or loader. The OLE slack anomaly and appended payload heuristics strongly suggest malicious intent. No VBA macros were extractable, but the appended payload is the primary indicator of compromise.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 79,872 bytes but its declared streams total only 16,543 bytes — 63,329 bytes (79%) 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.