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

Static analysis result for SHA-256 a95dc6b03ced446b…

MALICIOUS

Office (OLE) / .DOC

603.6 KB Created: 2001-12-14 14:26:00 Authoring application: Microsoft Word 9.0
MD5: 1d0131e0aa132ac00813731fdb3eef6d SHA-1: 51ba7f4c58bb745ac91bd8f09d4c0bd000d48f39 SHA-256: a95dc6b03ced446bcc5867e8760a5d11e0016382adf5705c90ff19c34dba873a
142 Risk Score

Malware Insights

MITRE ATT&CK
T1204.001 User Execution: Malicious Link T1204.002 User Execution: Malicious File

The file is a Microsoft Word document exhibiting OLE slack anomalies and an appended executable payload. Crucially, it triggers a critical heuristic for CVE-2006-6456, indicating exploitation of a known Microsoft Word vulnerability. No VBA macros were extractable, but the presence of appended payload bytes suggests the document is designed to drop and execute a secondary stage. The document body contains heavily garbled text, offering no discernible lure.

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 618,064 bytes but its declared streams total only 94,801 bytes — 523,263 bytes (85%) 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.