Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 e19c3f6ec5c21351…

MALICIOUS

Office (OLE)

120.4 KB Created: 2007-09-18 04:34:00 Authoring application: Microsoft Word 11.
MD5: 2ea486f5907e8a4dc3b8207ae66e49aa SHA-1: b2a9e3edc32ec83fa38b16291cd68b19e6b03cfc SHA-256: e19c3f6ec5c21351f299d3e1f1d52abcde12c46d7b73a37d834bd93a3694f734
82 Risk Score

Malware Insights

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

The OLE document exhibits anomalies in its slack space and contains appended executable-looking payload bytes, indicating it's likely a dropper. The VBA extraction failed due to an unsupported format, but the appended payload suggests the file's primary purpose is to deliver a secondary malicious component. The high entropy of the appended bytes further supports this.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 123,289 bytes but its declared streams total only 16,486 bytes — 106,803 bytes (87%) 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.