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

Static analysis result for SHA-256 3e16c36f00ee1bb6…

MALICIOUS

Office (OLE) / .DOC

77.0 KB Created: 2008-07-11 06:57:00 Authoring application: Microsoft Office Word
MD5: 2eff1d9803c9345d9df4c1f8d6a40ac9 SHA-1: d4013806355847db0a09d086be0c72c2f6f6ea1f SHA-256: 3e16c36f00ee1bb6be68225bba8e5f4f8a98276aa8f1dd73b8badfb81b9feef8
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The file is identified as a malicious OLE document due to a large unaccounted-for region and appended executable-looking payload bytes. Although VBA macros could not be extracted, the presence of appended executable data strongly indicates a malware delivery mechanism. The SHA256 hash of the file is included as a primary indicator.

Heuristics 3

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