Analysis
-
max time kernel
238s -
max time network
249s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
27-11-2022 01:31
Static task
static1
Behavioral task
behavioral1
Sample
34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe
Resource
win10v2004-20221111-en
General
-
Target
34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe
-
Size
1.1MB
-
MD5
bb45c49cf79a6397338844e57c6ef55e
-
SHA1
f10c69b23843f7e9baf9bd01cca464739e84d465
-
SHA256
34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b
-
SHA512
778ad5935f426ab285b677696ef6ef09ffa2fac461051bedd07f4016c88247125f693baca640934cb2a9cd688605f1f31e5cbed556342c1d89be1a6e699e72d1
-
SSDEEP
12288:euklkMVqd1t8jEIoCTaPG0j4DeuH5GyAw64vYr1IZq6T7UNU7hm92J6Gz1VwFAHe:e3jl2WzbZL6gEAqEVmA7x6FAnc
Malware Config
Signatures
-
Checks BIOS information in registry 2 TTPs 2 IoCs
BIOS information is often read in order to detect sandboxing environments.
description ioc Process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe -
Maps connected drives based on registry 3 TTPs 2 IoCs
Disk information is often read in order to detect sandboxing environments.
description ioc Process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4416 set thread context of 216 4416 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe 83 -
Suspicious use of SetWindowsHookEx 6 IoCs
pid Process 216 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe 216 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe 216 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe 216 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe 216 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe 216 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4416 wrote to memory of 216 4416 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe 83 PID 4416 wrote to memory of 216 4416 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe 83 PID 4416 wrote to memory of 216 4416 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe 83 PID 4416 wrote to memory of 216 4416 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe 83 PID 4416 wrote to memory of 216 4416 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe 83 PID 4416 wrote to memory of 216 4416 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe 83 PID 4416 wrote to memory of 216 4416 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe 83 PID 4416 wrote to memory of 216 4416 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe 83 PID 4416 wrote to memory of 216 4416 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe 83 PID 4416 wrote to memory of 216 4416 34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe"C:\Users\Admin\AppData\Local\Temp\34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe"1⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4416 -
C:\Users\Admin\AppData\Local\Temp\34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe"C:\Users\Admin\AppData\Local\Temp\34b2605e792e86970cfa8f8e0e7e827572b7435dd552f2ac00245eab29d7753b.exe" Track="0001001000"2⤵
- Suspicious use of SetWindowsHookEx
PID:216
-