MALICIOUS
380
Risk Score
Malware Insights
MITRE ATT&CK
T1059.001 PowerShell
T1055 Process Injection
T1105 Ingress Tool Transfer
The sample is an OLE document with a significant slack space anomaly and an embedded PE executable. Heuristics indicate the use of critical Windows API functions such as WriteProcessMemory and CreateRemoteThread, commonly used for process injection. The presence of an embedded executable strongly suggests the document is a dropper designed to execute a malicious payload. No scripts were extracted, limiting further analysis of the payload's specific behavior.
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 218,185 bytes but its declared streams total only 94,801 bytes — 123,384 bytes (57%) 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).
-
Embedded PE executable high OLE_EMBEDDED_EXEMZ/PE header found inside document — possible embedded executable
-
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.