Analysis
-
max time kernel
150s -
max time network
150s -
platform
windows10-2004_x64 -
resource
win10v2004-20240426-en -
resource tags
arch:x64arch:x86image:win10v2004-20240426-enlocale:en-usos:windows10-2004-x64system -
submitted
19-05-2024 06:51
Static task
static1
Behavioral task
behavioral1
Sample
34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe
Resource
win7-20240508-en
Behavioral task
behavioral2
Sample
34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe
Resource
win10v2004-20240426-en
General
-
Target
34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe
-
Size
9.5MB
-
MD5
6bbfea1a0d783a09f481f15ec81f54f5
-
SHA1
348b7a3cd4c9ccd21f7d435344922861fb25a150
-
SHA256
34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949
-
SHA512
e6a744d1646048a13286e99519936ad81f5ea1bfc5124050e9d74b346fbe22410a75d391f9c9f1ed7f76206d56ad9fac6c210a0c9d2f5fa4f5405f1deda324c7
-
SSDEEP
196608:nF+DGhrXoxPHrz4RLfqqhqDF6xIlg6fjphjbtAwbBvuiM:nF+DGhrXoxPHrMRLfqqoDFpln7rbt
Malware Config
Signatures
-
Banload
Banload variants download malicious files, then install and execute the files.
-
Identifies VirtualBox via ACPI registry values (likely anti-VM) 2 TTPs 1 IoCs
Processes:
34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exedescription ioc Process Key opened \REGISTRY\MACHINE\HARDWARE\ACPI\DSDT\VBOX__ 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe -
Checks BIOS information in registry 2 TTPs 2 IoCs
BIOS information is often read in order to detect sandboxing environments.
Processes:
34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exedescription ioc Process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosDate 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe -
Suspicious use of SetThreadContext 64 IoCs
Processes:
34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exedescription pid Process procid_target PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 set thread context of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 -
Program crash 8 IoCs
Processes:
WerFault.exeWerFault.exeWerFault.exeWerFault.exeWerFault.exeWerFault.exeWerFault.exeWerFault.exepid pid_target Process procid_target 1428 1816 WerFault.exe 82 1668 4160 WerFault.exe 89 2720 1816 WerFault.exe 82 3896 4160 WerFault.exe 89 3028 4160 WerFault.exe 89 2148 4160 WerFault.exe 89 4664 4160 WerFault.exe 89 5076 4160 WerFault.exe 89 -
Modifies registry class 9 IoCs
Processes:
34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exedescription ioc Process Key created \REGISTRY\MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{FCD6C80E-3F67-7AF0-51E8-F4257BF153AA} 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe Set value (str) \REGISTRY\MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{FCD6C80E-3F67-7AF0-51E8-F4257BF153AA}\ = "ADODB.Stream" 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe Set value (str) \REGISTRY\MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{FCD6C80E-3F67-7AF0-51E8-F4257BF153AA}\InprocServer32\ = "C:\\Program Files (x86)\\Common Files\\System\\ado\\msado15.dll" 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe Key created \REGISTRY\MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{FCD6C80E-3F67-7AF0-51E8-F4257BF153AA}\VersionIndependentProgID 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe Set value (str) \REGISTRY\MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{FCD6C80E-3F67-7AF0-51E8-F4257BF153AA}\VersionIndependentProgID\ = "ADODB.Stream" 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe Key created \REGISTRY\MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{FCD6C80E-3F67-7AF0-51E8-F4257BF153AA}\InprocServer32 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe Set value (str) \REGISTRY\MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{FCD6C80E-3F67-7AF0-51E8-F4257BF153AA}\InprocServer32\ThreadingModel = "Apartment" 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe Key created \REGISTRY\MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{FCD6C80E-3F67-7AF0-51E8-F4257BF153AA}\ProgID 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe Set value (str) \REGISTRY\MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{FCD6C80E-3F67-7AF0-51E8-F4257BF153AA}\ProgID\ = "ADODB.Stream.6.0" 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe -
Suspicious use of AdjustPrivilegeToken 4 IoCs
Processes:
34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exedescription pid Process Token: 33 4160 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe Token: SeIncBasePriorityPrivilege 4160 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe Token: 33 4160 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe Token: SeIncBasePriorityPrivilege 4160 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe -
Suspicious use of FindShellTrayWindow 1 IoCs
Processes:
34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exepid Process 4160 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe -
Suspicious use of SendNotifyMessage 1 IoCs
Processes:
34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exepid Process 4160 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe -
Suspicious use of SetWindowsHookEx 2 IoCs
Processes:
34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exepid Process 4160 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 4160 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe -
Suspicious use of WriteProcessMemory 5 IoCs
Processes:
34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exedescription pid Process procid_target PID 1816 wrote to memory of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 wrote to memory of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 wrote to memory of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 wrote to memory of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89 PID 1816 wrote to memory of 4160 1816 34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe 89
Processes
-
C:\Users\Admin\AppData\Local\Temp\34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe"C:\Users\Admin\AppData\Local\Temp\34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1816 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1816 -s 5562⤵
- Program crash
PID:1428
-
-
C:\Users\Admin\AppData\Local\Temp\34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe"C:\Users\Admin\AppData\Local\Temp\34614d74c87dd35699a46b00c6bab995dc95efa1035704415e4affb4eba38949.exe"2⤵
- Identifies VirtualBox via ACPI registry values (likely anti-VM)
- Checks BIOS information in registry
- Modifies registry class
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of FindShellTrayWindow
- Suspicious use of SendNotifyMessage
- Suspicious use of SetWindowsHookEx
PID:4160 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4160 -s 5563⤵
- Program crash
PID:1668
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4160 -s 7043⤵
- Program crash
PID:3896
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4160 -s 8563⤵
- Program crash
PID:3028
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4160 -s 8643⤵
- Program crash
PID:2148
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4160 -s 8963⤵
- Program crash
PID:4664
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4160 -s 9363⤵
- Program crash
PID:5076
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1816 -s 7002⤵
- Program crash
PID:2720
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 424 -p 1816 -ip 18161⤵PID:1680
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 524 -p 4160 -ip 41601⤵PID:4396
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 468 -p 1816 -ip 18161⤵PID:4404
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 516 -p 4160 -ip 41601⤵PID:868
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 508 -p 4160 -ip 41601⤵PID:2560
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 468 -p 4160 -ip 41601⤵PID:4864
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 536 -p 4160 -ip 41601⤵PID:1504
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 516 -p 4160 -ip 41601⤵PID:1072