MALICIOUS
360
Risk Score
Malware Insights
MITRE ATT&CK
T1204.002 Malicious File
The sample exhibits critical heuristic firings related to process injection (WriteProcessMemory, CreateRemoteThread) and library loading (LoadLibrary, GetProcAddress), indicating an attempt to execute malicious code. The OLE slack anomaly suggests potential obfuscation or padding within the file structure. While no specific document body content or scripts were clearly extracted, the API calls strongly suggest the file is designed to download and execute a secondary payload.
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 160,571 bytes but its declared streams total only 20,632 bytes — 139,939 bytes (87%) 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.