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

Static analysis result for SHA-256 c9c743c231f2f109…

MALICIOUS

Office (OLE) / .DOC

276.3 KB Created: 2008-07-11 06:57:00 Authoring application: Microsoft Office Word
MD5: 9c223c34107669d5950db38f8f998c28 SHA-1: 934c0e413ecb14ea6b308e757e20d78491872432 SHA-256: c9c743c231f2f10999bbc1f97ecc276062a760a1e0c2b392fdb30152fb8ea4f0
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1027 Obfuscated Files or Information

The OLE document exhibits significant slack space and an appended executable payload, indicating it's designed to deliver secondary malicious content. While VBA macros could not be extracted due to an unsupported format, the presence of the appended payload strongly suggests a dropper functionality. The file's SHA256 hash is included as a primary IOC.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 282,890 bytes but its declared streams total only 16,543 bytes — 266,347 bytes (94%) 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.