MALICIOUS
260
Risk Score
Malware Insights
MITRE ATT&CK
T1059.003 Windows Command Shell
T1059.001 PowerShell
T1218 System Binary Proxy Execution
T1071 Application Layer Protocol
T1055 Process Injection
The sample exhibits high-confidence heuristic firings indicating the use of critical Windows API functions for code execution and process manipulation, including WinExec, CreateProcess, LoadLibrary, and GetProcAddress. The suspicious invocation of cmd.exe with an execution flag further suggests the execution of arbitrary commands. The OLE slack anomaly indicates potential obfuscation or padding within the document structure. While no specific URLs or scripts were extracted, the API calls strongly suggest the document is designed to download and execute a second-stage payload.
Heuristics 7
-
Reference to WinExec API high SC_STR_WINEXECReference to WinExec API
-
Reference to CreateProcess API high SC_STR_CREATEPROCESSReference to CreateProcess API
-
Suspicious cmd.exe invocation with execution flag high SC_STR_CMDSuspicious cmd.exe invocation with execution flag
-
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 176,128 bytes but its declared streams total only 94,801 bytes — 81,327 bytes (46%) 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).
-
Reference to VirtualAlloc API medium SC_STR_VIRTUALALLOCReference to VirtualAlloc API
Open this report in the interactive analyzer, or submit your own file for analysis.