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

Static analysis result for SHA-256 c9928c88cb852090…

MALICIOUS

Office (OLE) / .DOC

103.5 KB Created: 2008-07-11 06:57:00 Authoring application: Microsoft Office Word
MD5: 233616cfe9038bb66963b9e184784704 SHA-1: 7a2f2f9089fe993e5c29a457856b23839ca33ada SHA-256: c9928c88cb852090396fea4be871753f07002ca742c2ff82026c9a3a590cf645
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The OLE document exhibits significant slack space and an appended executable payload, indicating its primary function is to deliver a secondary malicious file. The document body is minimal and non-descriptive. No VBA macros were extractable due to an unsupported format, preventing further analysis of script-based execution or persistence mechanisms.

Heuristics 3

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