MALICIOUS
82
Risk Score
Malware Insights
MITRE ATT&CK
T1204 Malicious File Execution
T1059 Command and Scripting Interpreter
The OLE document exhibits significant slack space and an appended payload, indicating a likely attempt to conceal malicious content. While VBA macros could not be extracted due to an unsupported format, the presence of these anomalies strongly suggests the file is designed to exploit a vulnerability and download a secondary payload. The exact nature of the payload and delivery mechanism remains unclear due to the inability to parse the macros.
Heuristics 3
-
OLE document has large unaccounted-for region high OLE_SLACK_ANOMALYOLE file is 203,776 bytes but its declared streams total only 16,486 bytes — 187,290 bytes (92%) 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_PAYLOADOLE 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_UNSUPPORTEDolevba 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.