MALICIOUS
300
Risk Score
Malware Insights
MITRE ATT&CK
T1059.003 Windows Command Shell
T1059.001 PowerShell
T1218.010 System Binary Proxy Execution: Regsvr32
The sample exhibits high-confidence heuristics indicating the use of WinExec, CreateProcess, VirtualAlloc, LoadLibrary, and GetProcAddress APIs, suggesting dynamic code execution. Notably, it references cmd.exe with an execution flag and contains visible LOLBin command execution instructions. This points to an attack pattern where the document likely attempts to download and execute a second-stage payload using Windows command-line utilities.
Heuristics 8
-
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 319,488 bytes but its declared streams total only 94,801 bytes — 224,687 bytes (70%) 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).
-
Visible LOLBin command execution instruction high SE_LOLBIN_RUN_COMMANDDocument contains instructions or visible command text involving Windows script/execution tools such as PowerShell, mshta, cmd, rundll32, or regsvr32
-
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.