MALICIOUS
360
Risk Score
Malware Insights
MITRE ATT&CK
T1059.001 PowerShell
T1059.003 Windows Command Shell
T1055 Process Injection
The sample exhibits strong indicators of malicious activity, including references to critical Windows API functions such as WriteProcessMemory, CreateRemoteThread, LoadLibrary, and GetProcAddress. These functions are commonly used for process injection, a technique to execute arbitrary code within another process. The presence of OLE Slack Anomaly also suggests potential obfuscation or padding within the document structure. While no specific family is identified, the techniques point towards a downloader or dropper mechanism.
Heuristics 9
-
Reference to WriteProcessMemory API critical SC_STR_WRITEPROCESSMEMORYReference to WriteProcessMemory API
-
Reference to CreateRemoteThread API critical SC_STR_CREATEREMOTETHREADReference to CreateRemoteThread API
-
Reference to WinExec API high SC_STR_WINEXECReference to WinExec API
-
Reference to CreateProcess API high SC_STR_CREATEPROCESSReference to CreateProcess 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 91,930 bytes but its declared streams total only 21,151 bytes — 70,779 bytes (77%) 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
-
Reference to VirtualProtect API medium SC_STR_VIRTUALPROTECTReference to VirtualProtect API
Open this report in the interactive analyzer, or submit your own file for analysis.