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

Static analysis result for SHA-256 6200938ae05c3a86…

MALICIOUS

Office (OLE) / .DOC

1.66 MB Created: 2001-12-14 14:26:00 Authoring application: Microsoft Word 9.0
MD5: f5bdd0593ac906ec19681f8c5491f0be SHA-1: c3519e948dd817c2542dcf04c595404e84ace073 SHA-256: 6200938ae05c3a865dd95f24e5d73458bbdc3159ca8d2243d6f93640afe08cdd
280 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1059 Command and Scripting Interpreter

The sample is a Microsoft Word document exhibiting a critical heuristic for CVE-2006-6456, indicating exploitation of a malformed table SPRM vulnerability. High-severity heuristics for ShellExecute, VirtualAlloc, LoadLibrary, and GetProcAddress suggest the execution of arbitrary code, likely a second-stage payload. The large slack space and appended payload further support this, indicating the file is designed to exploit this vulnerability for code execution.

Heuristics 7

  • 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 ShellExecute API high SC_STR_SHELLEXEC
    Reference to ShellExecute API
  • 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 1,739,200 bytes but its declared streams total only 94,801 bytes — 1,644,399 bytes (95%) 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.
  • Reference to VirtualAlloc API medium SC_STR_VIRTUALALLOC
    Reference to VirtualAlloc API

Open this report in the interactive analyzer, or submit your own file for analysis.