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

Static analysis result for SHA-256 db43ee2620f8058b…

MALICIOUS

Office (OLE) / .ASP

80.9 KB First seen: 2026-05-10
MD5: 16832f2ab9e49d3295751a2f7c3526f5 SHA-1: ac3ba887b71e5d7ecb3af0b6b4ef2463b9267b22 SHA-256: db43ee2620f8058b4d660e0fcc79306cbfa3cf45f27b4f16ce891269df4d8e6c
60 Risk Score

Heuristics 2

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 82,804 bytes but its declared streams total only 0 bytes — 82,804 bytes (100%) 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).
  • CFB header with no readable streams medium OLE_PARSE_EMPTY_STREAMS
    The file begins with a valid OLE2/CFB header but exposes no directory streams. A non-empty compound document with an unreadable directory is anomalous — it is seen with truncated/corrupt files and, more importantly, with content deliberately shifted off byte boundaries to defeat parsers while the host application still recovers the object.