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

Static analysis result for SHA-256 df802276cab16cec…

MALICIOUS

Office (OLE) / .DOC

123.9 KB Created: 2007-09-18 04:34:00 Authoring application: Microsoft Word 11.
MD5: c9665bb4be0c607ceea0df6eaddf84a1 SHA-1: aecec9a9ba42ae57b87d1b1adfdc382952284ccb SHA-256: df802276cab16cec2f36aae0aff585bea3e06cb42df5861a66dea4b6304ac093
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The OLE document exhibits anomalies including a large slack region and appended executable-looking payload bytes. The file type is a legacy Microsoft Word document, and VBA extraction failed, suggesting potential obfuscation or encryption. The presence of appended payload bytes strongly indicates the file's purpose is to deliver a secondary malicious payload.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 126,873 bytes but its declared streams total only 16,486 bytes — 110,387 bytes (87%) 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.

Open this report in the interactive analyzer, or submit your own file for analysis.