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

Static analysis result for SHA-256 bada232b3e77fb9a…

MALICIOUS

Office (OLE) / .DOC

99.9 KB Created: 2005-06-29 18:14:00 Authoring application: Microsoft Word 10.0
MD5: 55745d870b359b5447ba0e4de8ea1e98 SHA-1: decc96a79ca0cbb7c78c56f52d5592ca03ebe379 SHA-256: bada232b3e77fb9a88d4d2ab8ee6d113fdaa88c39431446cdb823b4bd83ba8a6
82 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The OLE document has a significant slack space and an appended executable-looking payload, indicating it likely serves as a dropper or loader. While VBA macros could not be extracted due to format issues, the presence of an embedded URL and the appended payload strongly suggest a malicious intent to deliver a secondary stage. The exact payload and delivery mechanism remain unclear without further analysis of the appended bytes.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 102,286 bytes but its declared streams total only 20,632 bytes — 81,654 bytes (80%) 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.