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

Static analysis result for SHA-256 ee4e915ae8a1191c…

MALICIOUS

Office (OLE) / .DOC

796.0 KB Created: 2009-06-05 16:16:00 Authoring application: Microsoft Office Word
MD5: f64cee0e7ce1218d93840685f54277aa SHA-1: 8c6e7f002841155a8dafbdc9b8af7a185bbb7323 SHA-256: ee4e915ae8a1191c614da3ab64cc8fcd99acc861449f371246d17faa1ddd89aa
82 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The file is an OLE document with a significant amount of appended data, indicating a potential embedded payload. The document body is a lure for training instructions, which is a common social engineering tactic. While no VBA macros were extractable, the presence of an appended payload and the OLE slack anomaly strongly suggest malicious intent. The file's SHA256 hash is included as a primary IOC.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 815,104 bytes but its declared streams total only 305,839 bytes — 509,265 bytes (62%) 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.