Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 5152c16c1dad005a…

MALICIOUS

Office (OLE)

172.3 KB Created: 2001-12-14 14:26:00 Authoring application: Microsoft Word 9.0
MD5: 6702594c3d93690c6f76e0d92a628578 SHA-1: fa708fc04fa55f533836cbd8f439fd253b39996a SHA-256: 5152c16c1dad005a01659e891df49556efe4b5a8d9195f8e5096e1557b2cf0fb
142 Risk Score

Malware Insights

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

The file is an OLE document with significant slack space and an appended executable payload, indicating it's designed to deliver malicious content. A critical heuristic firing points to CVE-2006-6456, a vulnerability in Microsoft Word related to malformed table SPRMs, which is likely the exploitation vector. No VBA macros could be extracted, but the appended payload suggests the document's purpose is to execute arbitrary code upon opening.

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 176,388 bytes but its declared streams total only 94,801 bytes — 81,587 bytes (46%) 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.