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

Static analysis result for SHA-256 224a19568855a6c8…

MALICIOUS

Office (OLE) / .DOC

66.0 KB Created: 2008-07-11 06:57:00 Authoring application: Microsoft Office Word
MD5: daf16179ef7bcc30bb350066c0495d92 SHA-1: b0ef172a9405fca59bb6bb9486c8587d721bb4b6 SHA-256: 224a19568855a6c858733bc5c41a86f691dbd1688cb27e513a6d01b0e270ffc3
82 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The OLE document exhibits anomalies in its slack space and contains an appended executable payload, indicating a likely attempt to conceal malicious content. While VBA macros could not be extracted, the presence of an embedded URL suggests a social engineering lure. The exact execution mechanism remains unclear due to the inability to parse macros, but the overall pattern points to a downloader or dropper.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 67,584 bytes but its declared streams total only 16,543 bytes — 51,041 bytes (76%) 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.