MALICIOUS
82
Risk Score
Malware Insights
MITRE ATT&CK
T1566.002 Spearphishing Attachment
The OLE file exhibits significant slack space and appended payload bytes, strongly suggesting it's a malicious container. While VBA macros could not be extracted due to an unsupported format, the presence of these anomalies points to a likely attempt to conceal and deliver a secondary malicious payload. The file's structure and the nature of the anomalies are consistent with common techniques used to distribute malware.
Heuristics 3
-
OLE document has large unaccounted-for region high OLE_SLACK_ANOMALYOLE file is 168,448 bytes but its declared streams total only 16,486 bytes — 151,962 bytes (90%) 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.