MALICIOUS
208
Risk Score
Malware Insights
MITRE ATT&CK
T1059.005 Visual Basic
T1547.001 Registry Run Keys / Startup Folder
The sample contains a Workbook_Open VBA macro, a common technique for executing malicious code upon opening an Office document. The macro utilizes CreateObject to interact with the file system and attempts to write a file named 'qOLEDBQuery.xsl' to the ALLUSERSPROFILE directory. It also appears to attempt persistence by writing to the registry run key 'HKCU\Software\Microsoft\Windows\CurrentVersion\Run\IAccessible2Proxy'. The obfuscated nature of the script and the use of generic function names make precise family attribution difficult.
Heuristics 6
-
LOLBin reference in VBA critical OLE_VBA_LOLBINLOLBin reference in VBA
-
Workbook_Open macro high OLE_VBA_WBOPENWorkbook_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 project inside OOXML medium OOXML_VBADocument contains a VBA project — VBA macros present
-
Environ() call (env variable access) low OLE_VBA_ENVIRONEnviron() call (env variable access)
Extracted artifacts 2
Files carved from inside the sample during analysis.
| Filename | Kind | Source | Size |
|---|---|---|---|
macros.bas3a9ad8abe7e7f0979fce26f375909f9118183a08d965138f280c318d3e9b9f4e |
vba-macro | oletools.olevba.extract_macros (decoded VBA source from OOXML) | 3632 bytes |
vbaProject_00.bin3b377156842cce5c39ee0d8c35329c652dcac05cc3c4b10bf1e0cea805137311 |
vba-project | OOXML VBA project: xl/vbaProject.bin | 16896 bytes |
Open this report in the interactive analyzer, or submit your own file for analysis.