MALICIOUS
82
Risk Score
Malware Insights
MITRE ATT&CK
T1566.002 Spearphishing Attachment
T1027 Obfuscated Files or Information
T1105 Ingress Tool Transfer
The OLE document exhibits a significant slack space anomaly and contains an appended executable payload, indicating it's a container for malicious code. The inability to extract VBA macros suggests obfuscation or a legacy format, further supporting a malicious intent. The primary IOC is the file's SHA256 hash, as no other indicators were extracted.
Heuristics 3
-
OLE document has large unaccounted-for region high OLE_SLACK_ANOMALYOLE file is 475,235 bytes but its declared streams total only 26,491 bytes — 448,744 bytes (94%) 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.