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

Static analysis result for SHA-256 316583ae10d057d0…

MALICIOUS

Office (OLE) / .DOC

241.5 KB Created: 2001-12-14 14:26:00 Authoring application: Microsoft Word 9.0
MD5: 99ca1cf15c9d8557e3181dea28717581 SHA-1: 4bdcb3fb35e2cb0fdbcd23663e8d75f778af1810 SHA-256: 316583ae10d057d014c65faf2fe2c09a38263f51a4c57b13743d328ed601cdfa
142 Risk Score

Malware Insights

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

The file is a Microsoft Word document exhibiting several high-severity heuristics, including OLE slack anomaly and an appended executable payload. Crucially, it triggers a critical alert for CVE-2006-6456, indicating exploitation of a malformed table vulnerability. No VBA macros were extractable, but the appended payload suggests the document is a dropper for further malicious activity. The document body contains heavily corrupted or non-readable 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 247,296 bytes but its declared streams total only 94,801 bytes — 152,495 bytes (62%) 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.