MALICIOUS
260
Risk Score
Malware Insights
MITRE ATT&CK
T1204.002 Malicious File
T1071.001 Web Protocols
The sample exhibits high-confidence heuristics indicating the execution of external code, including references to CreateProcess, ShellExecute, VirtualAlloc, LoadLibrary, and GetProcAddress APIs. The OLE structure also shows an appended payload, suggesting the document is a loader for a secondary executable. No document body text was available for analysis, and no scripts were extracted.
Heuristics 7
-
Reference to CreateProcess API high SC_STR_CREATEPROCESSReference to CreateProcess API
-
Reference to ShellExecute API high SC_STR_SHELLEXECReference to ShellExecute 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 147,360 bytes but its declared streams total only 21,151 bytes — 126,209 bytes (86%) 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).
-
OLE file has appended executable-looking payload bytes high OLE_APPENDED_PAYLOADOLE compound file contains a large high-entropy region beyond the declared major streams and that region includes shellcode, PE, or loader API markers. This is a payload-carrier signal, not a specific CVE attribution by itself.
-
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.