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

Static analysis result for SHA-256 8e6a69441a1ced70…

MALICIOUS

Office (OLE) / .DOC

87.0 KB Created: 2008-07-11 06:57:00 Authoring application: Microsoft Office Word
MD5: 2717a17409f08fd112c01998bd491033 SHA-1: 13c1b55b2c18349bbe5ce41d4d1d9487507c2c65 SHA-256: 8e6a69441a1ced70ab4ce015ab489ade4a6a1a9c3428fc63c1a5d9b3997520ee
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The OLE document exhibits significant slack space and appended payload bytes, indicating it's likely a container for a malicious executable. The 'OFFICE_FORMAT_UNSUPPORTED' heuristic suggests that VBA macros could not be extracted, which is common for certain types of malicious Office documents. The presence of appended payload bytes is a strong indicator of malicious intent, though the specific family cannot be determined without further analysis of the payload.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 89,110 bytes but its declared streams total only 16,543 bytes — 72,567 bytes (81%) 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.