MALICIOUS
360
Risk Score
Malware Insights
MITRE ATT&CK
T1055 Process Injection
T1204.002 Malicious File
The sample is a malicious Office document that exhibits strong indicators of process injection. Heuristics indicate the use of critical Windows API functions such as WriteProcessMemory and CreateRemoteThread, along with LoadLibrary and GetProcAddress, suggesting the loading and execution of a secondary payload. The large slack space in the OLE structure further supports the possibility of embedded malicious content. No document body or script content was available for analysis, limiting the ability to identify specific lures or obfuscation techniques.
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 79,700 bytes but its declared streams total only 21,151 bytes — 58,549 bytes (73%) 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.