MALICIOUS
220
Risk Score
Malware Insights
MITRE ATT&CK
T1059.001 PowerShell
T1204.002 Malicious File
T1027 Obfuscated Files or Information
The sample exhibits characteristics of a malicious Office document, including a large slack space anomaly and references to WinExec, LoadLibrary, and GetProcAddress APIs, suggesting dynamic code loading. The presence of XOR-encoded strings with a key of 0x03 indicates obfuscation techniques are in use. While no specific exploit is identified, these indicators point towards an attempt to execute arbitrary code, likely to download and run a secondary payload.
Heuristics 5
-
XOR-encoded strings (key 0x03) critical SC_XOR_ENCODEDFound 8 Windows library/API name(s) XOR-encoded with single-byte key 0x03: 'VirtualAlloc', 'VirtualAlloc', 'VirtualAllocEx', 'VirtualProtect', 'VirtualProtectEx', 'CreateProcessA', 'WriteProcessMemory', 'ReadProcessMemory'
-
Reference to WinExec API high SC_STR_WINEXECReference to WinExec API
-
Reference to LoadLibrary API high SC_STR_LOADLIBRARYReference to LoadLibrary API
-
Reference to GetProcAddress API high SC_STR_GETPROCADDRESSReference to GetProcAddress API
-
OLE document has large unaccounted-for region high OLE_SLACK_ANOMALYOLE file is 428,544 bytes but its declared streams total only 31,351 bytes — 397,193 bytes (93%) 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.