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

Static analysis result for SHA-256 6546e81cd1cfdd59…

MALICIOUS

Office (OLE) / .DOC

235.2 KB Created: 2001-12-14 14:26:00 Authoring application: Microsoft Word 9.0
MD5: 9c1b106f05764289a44bc661fc2fa881 SHA-1: 41ebd966b4305677b312ea02c1be5bdc2ed5b250 SHA-256: 6546e81cd1cfdd59076cb07f26e7bf409d2e2a6c5fd6ed04171ab1ca09dd3f94
220 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The sample is a malicious Microsoft Word document that leverages CVE-2006-6456, a vulnerability related to malformed table SPRMs, to achieve code execution. The presence of LoadLibrary and GetProcAddress API references, along with an appended executable payload and significant slack space, indicates the document is designed to drop and run a secondary stage. No document body or script content was available for further analysis.

Heuristics 5

  • 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.
  • Reference to LoadLibrary API high SC_STR_LOADLIBRARY
    Reference to LoadLibrary API
  • Reference to GetProcAddress API high SC_STR_GETPROCADDRESS
    Reference to GetProcAddress API
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 240,896 bytes but its declared streams total only 94,801 bytes — 146,095 bytes (61%) 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.