Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 803f4cfef8344da8…

MALICIOUS

Office (OLE)

102.0 KB Created: 2008-07-11 06:57:00 Authoring application: Microsoft Office Word
MD5: 5a35b53e406b38e5a7d12f12b6e3ec8a SHA-1: 6e1f215b6615fcac92484d0f27b391df88a1e17d SHA-256: 803f4cfef8344da80a8cd4742f8c50b99bec6f9cc0307185de46d5ab83fe2dfd
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The OLE document exhibits a large slack region and appended executable payload bytes, indicating it is likely a malicious dropper. While VBA macros could not be extracted due to an unsupported format, the presence of appended payload strongly suggests the file's intent is to deliver a secondary stage. 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 104,448 bytes but its declared streams total only 16,543 bytes — 87,905 bytes (84%) 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.