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

Static analysis result for SHA-256 78a138e357909147…

MALICIOUS

Office (OLE) / .DOC

222.2 KB Created: 2001-12-14 14:26:00 Authoring application: Microsoft Word 9.0
MD5: 226acbefae429d643a73bfb91db20b8c SHA-1: 76298fa3a47d87505b86a67f6382660262e040b8 SHA-256: 78a138e357909147149cbc39402520a9f9154fa6eae3fcbd2fdc8afeba3cb363
142 Risk Score

Malware Insights

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

The file is a Microsoft Word document exhibiting characteristics of an appended executable payload and a malformed table structure, indicative of an exploit. Specifically, the CVE-2006-6456 heuristic firing points to exploitation for client execution. The presence of appended payload bytes suggests the document is designed to deliver and execute a secondary stage. Given the nature of the exploit and the likely delivery method, it is classified as a malicious document likely delivered via spearphishing.

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 227,534 bytes but its declared streams total only 94,801 bytes — 132,733 bytes (58%) 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.
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://schemas.openxmlformats.org/drawingml/2006/main

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