MALICIOUS
260
Risk Score
Malware Insights
MITRE ATT&CK
T1059.005 Visual Basic
T1059.001 PowerShell
T1218.011 System Binary Proxy Execution: Rundll32
T1059.003 Windows Command Shell
The sample is an Excel document containing a Workbook_Open macro. This macro references PowerShell and cmd.exe, and uses GetObject and CreateObject to launch a WMI process. This indicates the macro is designed to execute a second-stage payload, likely PowerShell, to further compromise the system. The VBA code itself appears to be obfuscated, suggesting an attempt to evade detection.
Heuristics 6
-
PowerShell reference in VBA critical OLE_VBA_PSPowerShell reference in VBA
-
VBA WMI Win32_Process launcher critical OLE_VBA_WMI_PROCESS_CREATEVBA macro builds or references a WMI moniker for Win32_Process and invokes .Create to start a command. This is a high-confidence macro execution chain that often hides the WMI class name through string concatenation or helper functions.
-
Workbook_Open macro high OLE_VBA_WBOPENWorkbook_Open macro
-
GetObject call high OLE_VBA_GETOBJGetObject call
-
cmd.exe reference in VBA high OLE_VBA_CMDcmd.exe reference in VBA
-
VBA project inside OOXML medium OOXML_VBADocument contains a VBA project — VBA macros present
Extracted artifacts 2
Files carved from inside the sample during analysis.
| Filename | Kind | Source | Size |
|---|---|---|---|
macros.basce66abc42c13fa27b4e8f88450c368cf3f931caa85ec3f07ba96e65561a9e736 |
vba-macro | oletools.olevba.extract_macros (decoded VBA source from OOXML) | 35434 bytes |
vbaProject_00.binb1069a61f392474a615169dcaa8a7f87f772712ab623bf32b8c799b36516d6bf |
vba-project | OOXML VBA project: xl/vbaProject.bin | 11776 bytes |
Open this report in the interactive analyzer, or submit your own file for analysis.