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

Static analysis result for SHA-256 efef44764a4a8d86…

MALICIOUS

Office (OLE) / .DOC

109.0 KB Created: 2008-07-11 06:57:00 Authoring application: Microsoft Office Word
MD5: bd3cdd6e88883f5df6f3f309c36ff406 SHA-1: f0592878167deaf000e372b636ddb75dc7b00c77 SHA-256: efef44764a4a8d8636d41cf0a9d9f16ca6bc06ba5a15b8cb10825500957e03f6
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The OLE document exhibits anomalies with a large amount of slack space and appended payload bytes, indicating it's likely a container for malicious code. The file type is a legacy Office document, and VBA extraction failed, suggesting a potential attempt to evade macro analysis. The appended payload bytes have high entropy, characteristic of packed or encrypted malicious code.

Heuristics 3

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