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

Static analysis result for SHA-256 daa899edee7e481b…

MALICIOUS

Office (OLE) / .DOC

899.0 KB Created: 2005-06-29 18:14:00 Authoring application: Microsoft Word 10.0
MD5: 2744d99b3c04c001c7e31a31dfd60d3e SHA-1: 7872ac75f58e61210659a0b2d6bb1e2fd5dcbfed SHA-256: daa899edee7e481bdd94df4690d89bf237570261f9390d725fc34b4f15160cab
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1027 Obfuscated Files or Information T1105 Ingress Tool Transfer

The OLE document exhibits a large slack region and an appended executable-looking payload, strongly suggesting it is a malicious dropper. While VBA macros could not be extracted due to an unsupported format, the presence of appended payload bytes indicates the file's intent is to deliver and execute additional malicious code. The SHA256 hash is included as a primary identifier.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 920,596 bytes but its declared streams total only 20,632 bytes — 899,964 bytes (98%) 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.