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

Static analysis result for SHA-256 05438403f3b7c776…

MALICIOUS

Office (OLE) / .DOC

537.6 KB Created: 2001-12-14 14:26:00 Authoring application: Microsoft Word 9.0
MD5: 1911a917ee6f47a0caede07b99f1a2b2 SHA-1: c0b8232c196e26c62fb4bea48f9d47b779a4c508 SHA-256: 05438403f3b7c776384e3f6bdf6ed5f22ddf930ac7a9ee01ac71b46d246aa5cb
140 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The file is a Microsoft Word document containing a malformed table SPRM, which is a known vulnerability (CVE-2006-6456) that allows for arbitrary code execution. The document also exhibits an unusually large slack space and an appended executable-looking payload, further indicating malicious intent. The presence of these indicators strongly suggests the file is designed to exploit this vulnerability for initial execution, likely delivered via spearphishing.

Heuristics 3

  • 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 550,480 bytes but its declared streams total only 94,801 bytes — 455,679 bytes (83%) 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.