Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 dabbfbdadacd6f51…

MALICIOUS

Office (OLE)

118.5 KB Created: 2007-12-03 01:19:00
MD5: e7cb3e08761b667ef1e17c5bce949f77 SHA-1: afa1e83e47d4b0fc802b0b3fb501de0f291e4732 SHA-256: dabbfbdadacd6f5191d88fc8181bcce8832603d1c9cdc1a6aa2ee2c7684ceb6a
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.002 Spearphishing Attachment T1027 Obfuscated Files or Information

The OLE file exhibits a significant amount of slack space and an appended payload, indicating it's likely a container for malicious content. The heuristic firings suggest the file is malformed or encrypted, preventing VBA macro extraction, but the appended payload strongly implies a downloader or dropper functionality. No document body text or scripts were available for further analysis.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 121,344 bytes but its declared streams total only 12,766 bytes — 108,578 bytes (89%) 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.

Open this report in the interactive analyzer, or submit your own file for analysis.