MALICIOUS
82
Risk Score
Malware Insights
MITRE ATT&CK
T1566.001 Spearphishing Attachment
T1059.005 Visual Basic
This OLE document exhibits anomalies indicative of malicious intent, including a large unaccounted-for region and appended executable-looking payload bytes. Although VBA macros could not be extracted due to format issues, the presence of these indicators suggests the file is designed to deliver a secondary payload. The SHA256 hash is included as a primary IOC.
Heuristics 3
-
OLE document has large unaccounted-for region high OLE_SLACK_ANOMALYOLE file is 74,307 bytes but its declared streams total only 23,753 bytes — 50,554 bytes (68%) 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.
Extracted artifacts 1
Files carved from inside the sample during analysis.
| Filename | Kind | Source | Size |
|---|---|---|---|
macros.bas158e0c514a66f35365eccab22137253bf8127fdc2d792eec9f5cff9a027fdbe6 |
vba-macro | oletools.olevba.extract_macros (decoded VBA source) | 387 bytes |
Open this report in the interactive analyzer, or submit your own file for analysis.