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

Static analysis result for SHA-256 47b62734501d35a7…

MALICIOUS

Office (OLE) / .DOC

163.3 KB Created: 2001-12-14 14:26:00 Authoring application: Microsoft Word 9.0
MD5: cfc497050e4e9f3cd61eaf78c199f8f3 SHA-1: 40c7091b5609206e5a0ec926c1196a9d20155386 SHA-256: 47b62734501d35a746de4b581353aa39425e6203ab5171f4ef73e2065221c9f0
142 Risk Score

Malware Insights

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

The file is identified as malicious due to a critical heuristic firing for CVE-2006-6456, indicating exploitation of a malformed table structure in Microsoft Word. Additionally, high severity heuristics detected an OLE slack anomaly and an appended executable-looking payload. No VBA macros could be extracted, but the presence of these indicators strongly suggests the document is designed to execute arbitrary code upon opening, likely leading to the download and execution of a second-stage payload.

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 167,172 bytes but its declared streams total only 94,801 bytes — 72,371 bytes (43%) 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.

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