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

Static analysis result for SHA-256 ea2c790369bed342…

MALICIOUS

Office (OLE) / .DOC

610.0 KB Created: 2001-12-14 14:26:00 Authoring application: Microsoft Word 9.0
MD5: 6bb11ff5a844c589ccd75d126b293e47 SHA-1: cab191a926ed11b40c7e4b9a6f16a8115037df60 SHA-256: ea2c790369bed3420fad97c87671ba345870588b072a21f3d5ba1be29dedd983
102 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File: User Execution: Malicious File T1566.001 Phishing: Spearphishing Attachment

The file is a Microsoft Word document exhibiting a critical vulnerability (CVE-2006-6456) related to malformed tables, indicating it's designed to exploit this flaw. The large slack space anomaly further suggests potential obfuscation or embedded malicious content. No VBA macros were extractable, but the presence of the exploit indicates a malicious intent to compromise the user's system upon opening.

Heuristics 3

  • 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 624,640 bytes but its declared streams total only 94,801 bytes — 529,839 bytes (85%) 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).
  • 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.