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

Static analysis result for SHA-256 ddee6899ab7827c1…

MALICIOUS

Office (OLE) / .DOC

796.0 KB Created: 2009-06-05 16:16:00 Authoring application: Microsoft Office Word
MD5: 48f547cf496b0f2cf919e12c5b57d924 SHA-1: 3aa045ce7d40485fe5d3f6d542cab48f9b4300df SHA-256: ddee6899ab7827c1d7f3fe0062d46e84e7d9d45bd799d0d9a4986ec585f8fa85
82 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The file is an OLE document with a large slack space and an appended executable payload, indicating it's likely a dropper. No VBA macros were extractable due to an unsupported format, but the appended payload suggests the file's primary purpose is to deliver and execute a secondary stage. The document body is a benign-looking training invitation, serving as a lure.

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.