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

Static analysis result for SHA-256 1c956c5d2e718ac1…

MALICIOUS

Office (OLE) / .DOC

114.5 KB Created: 2008-07-11 06:57:00 Authoring application: Microsoft Office Word
MD5: a6952e9072aa11d448d6de411018dab0 SHA-1: e813a553658844e86dff1ef6c4919a57700e796c SHA-256: 1c956c5d2e718ac11b3b744784c101271c275a068ec5382919bff9a98b555bad
82 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The OLE document exhibits anomalies with a large slack region and an appended executable-looking payload, indicating the presence of hidden malicious code. While VBA macros could not be extracted due to an unsupported format, the embedded URL heuristic suggests a delivery mechanism. The appended payload strongly suggests the file is designed to download and execute a second-stage payload.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 117,248 bytes but its declared streams total only 16,543 bytes — 100,705 bytes (86%) 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.