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

Static analysis result for SHA-256 19efb7d5d102bf27…

MALICIOUS

Office (OLE) / .DOC

85.3 KB Created: 2008-07-11 06:57:00 Authoring application: Microsoft Office Word
MD5: dc4e93ba6fa8ec44dbe5d214e3642172 SHA-1: 437066ae1915e8e8accaebdf3a1d6fe7b671dba2 SHA-256: 19efb7d5d102bf27a820146ea9080cc1de5580b377fe9e65a272b51c97238be7
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The OLE document exhibits significant slack space and appended payload bytes, indicating it's likely a dropper or container for malicious code. While VBA macros could not be extracted due to an unsupported format, the presence of these anomalies strongly suggests the file's malicious intent. The SHA256 hash is included as a primary IOC.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 87,306 bytes but its declared streams total only 16,543 bytes — 70,763 bytes (81%) 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.