MALICIOUS
140
Risk Score
Malware Insights
The file is a malicious Office document exhibiting a NOP sled and XOR-encoded strings, indicating a likely attempt to obfuscate malicious code. The large amount of slack space in the OLE structure further suggests the presence of embedded, potentially malicious, content. Without a document body or script content, the exact payload and delivery mechanism remain unclear, but the heuristics strongly point to code execution.
Heuristics 3
-
XOR-encoded strings (key 0x95) critical SC_XOR_ENCODEDFound 2 Windows library/API name(s) XOR-encoded with single-byte key 0x95: 'LoadLibraryA', 'GetProcAddress'
-
NOP sled detected high SC_NOP_SLEDFound 20+ consecutive 0x90 bytes
-
OLE document has large unaccounted-for region high OLE_SLACK_ANOMALYOLE file is 265,839 bytes but its declared streams total only 16,486 bytes — 249,353 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).
Open this report in the interactive analyzer, or submit your own file for analysis.