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

Static analysis result for SHA-256 9895f2058f01cde0…

MALICIOUS

Office (OLE) / .DOC

169.8 KB Created: 2001-12-14 14:26:00 Authoring application: Microsoft Word 9.0
MD5: 33e00cccd787bcfa7c66ed587b6a8af0 SHA-1: 3251aae82236094c1ee7b7e3c91f1287158ad304 SHA-256: 9895f2058f01cde03d765ca037c9afc3593022e30236e1b857fe3b1b70daa528
142 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File T1059.001 PowerShell

The file is a Microsoft Word document exhibiting an OLE slack anomaly and an appended executable payload. A critical heuristic identified the CVE-2006-6456 vulnerability, indicating exploitation of a malformed table structure within the document. No VBA macros were extractable, but the presence of an appended payload suggests the document is designed to drop and execute further malicious code. The document body contains heavily corrupted text, providing no contextual clues.

Heuristics 4

  • CVE-2006-6456 — Microsoft Word malformed table SPRM critical CVE exact CVE_2006_6456
    WordDocument contains a malformed table border-color SPRM in the CVE-2006-6456 shape: a valid table-SPRM cluster is followed by an invalid high-byte 0xFF SPRM where Word expects a normal sprmTBrc*Cv record. Vulnerable Word 2000/2002/2003 parsers corrupt memory while handling this malformed data structure.
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 173,828 bytes but its declared streams total only 94,801 bytes — 79,027 bytes (45%) 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.