MALICIOUS
300
Risk Score
Malware Insights
MITRE ATT&CK
T1059.005 Visual Basic
T1140 Deobfuscate/Decode Files or Information
T1055.012 Process Injection: Process Hollowing
T1547.001 Registry Run Keys / Startup Folder: Registry Run Keys / Startup Folder
The sample is an Excel file containing VBA macros that are triggered by Auto_Open and Document_Open. The macros use CreateObject("wScript.Shell") to write a base64-encoded payload to the user's AppData\Local\Microsoft\Windows\Apps directory, unzip it, and then execute it. Persistence is established by creating a registry Run key pointing to the extracted executable.
Heuristics 7
-
Shell() call in VBA critical OLE_VBA_SHELLShell() call in VBA
-
Dangerous API name reassembled from split string literals critical OLE_VBA_SPLIT_KEYWORD_OBFUSCATIONVBA concatenates short string literals that reassemble a dangerous API/ProgID/LOLBin name (e.g. Scripting.FileSystemObject, WScript.Shell, powershell, URLDownloadToFile) which appears in no single literal. Splitting an API name across string concatenation is done only to evade keyword scanning.
-
Document_Open macro high OLE_VBA_DOCOPENDocument_Open macro
-
Auto_Open macro high OLE_VBA_AUTOAuto_Open macro
-
CreateObject call high OLE_VBA_CREATEOBJCreateObject call
-
VBA p-code auto-exec with execution tokens high OLE_VBA_PCODE_AUTOEXEC_EXECCompiled VBA/cache stream contains an auto-execution token together with shell/download/object-execution tokens. This catches p-code-only or source-extraction-failure macro documents where visible source is unavailable.
-
VBA macros detected medium OLE_VBA_MACROSDocument contains VBA macro code
Extracted artifacts 1
Files carved from inside the sample during analysis.
| Filename | Kind | Source | Size |
|---|---|---|---|
macros.bas4dcebe827968903a33992315b7b73f2123987e627cb222f0c9be7a7a41957f4f |
vba-macro | oletools.olevba.extract_macros (decoded VBA source) | 363034 bytes |
Open this report in the interactive analyzer, or submit your own file for analysis.