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

Static analysis result for SHA-256 8a2dfd79cc738018…

MALICIOUS

Office (OLE) / .DOC

98.0 KB Created: 2008-07-11 06:57:00 Authoring application: Microsoft Office Word
MD5: 7646e7a658b489d7b39c594415d70a53 SHA-1: 23a75daf57f86b0ae2ddf15f85a002958aebeac9 SHA-256: 8a2dfd79cc7380188728803e3d7e13fdd7f36362d64961f4bf2ca2adfe3fca8a
82 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The OLE document exhibits a large slack space and appended executable-looking payload bytes, indicating it's a container for malicious content. Although VBA macros could not be extracted, the presence of an appended payload strongly suggests the file is designed to deliver malware. The SHA256 hash is included as a primary indicator.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 100,352 bytes but its declared streams total only 16,543 bytes — 83,809 bytes (84%) 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.