Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 8e78b49165958212…

MALICIOUS

Office (OLE)

84.7 KB Created: 2008-07-11 06:57:00 Authoring application: Microsoft Office Word
MD5: 0af564625da0ad8c0547b4325dd1df99 SHA-1: 53fa7cd32ff5cfe1f2e6b67ea91428bed45f1eac SHA-256: 8e78b49165958212f53fb03ddf5d3b56c21b917429c14ec5b98055aab612def3
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The OLE file exhibits a large slack region and appended executable payload bytes, strongly indicating it's a malicious container. Although VBA macros could not be extracted due to an unsupported format, the presence of appended payload suggests the file is intended to deliver malware. 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 86,778 bytes but its declared streams total only 16,543 bytes — 70,235 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.

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