Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 510250d632434a78…

MALICIOUS

Office (OLE)

240.0 KB Created: 2007-09-18 04:34:00 Authoring application: Microsoft Word 11.
MD5: 0ecbabdca1321010d91e26e7d123d9ee SHA-1: ddfcdcece46a4ce87b83fe056b91e1812dbe6e39 SHA-256: 510250d632434a78138163e7523346c623d488255b7aa75c13ccc57c96a914ef
82 Risk Score

Malware Insights

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

The OLE file exhibits significant slack space and an appended executable-looking payload, indicating a likely attempt to hide malicious content. The file format is also flagged as unsupported for VBA extraction, suggesting potential obfuscation or legacy structure. While no specific document body content or scripts were extractable, the structural anomalies strongly suggest the file is designed to deliver a secondary payload.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 245,760 bytes but its declared streams total only 16,486 bytes — 229,274 bytes (93%) 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.