Analysis
-
max time kernel
196s -
max time network
213s -
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, 03:38
Static task
static1
Behavioral task
behavioral1
Sample
2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe
Resource
win10v2004-20221111-en
General
-
Target
2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe
-
Size
1.0MB
-
MD5
45165344f53e7910f1d17ca0b28b080c
-
SHA1
45b530f19ccf048e2c8bd474b4e8ac80086a36c8
-
SHA256
2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c
-
SHA512
5ef97dd2ca655346009e33c5e0d7d75ebdd1ea1d2e930db8b02988d02d5f6708185d8bca7f4fd5f4ddbd7932b20ae04c0c05a6810835ab68c2df7102180c2f4c
-
SSDEEP
24576:zlafNPaNMDJOpKROZRpulZBVOkeOLimGHCmO+n:RaANaRGRpuHetmGimZn
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 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.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 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4576 set thread context of 936 4576 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe 83 -
Suspicious use of SetWindowsHookEx 6 IoCs
pid Process 936 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe 936 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe 936 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe 936 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe 936 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe 936 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4576 wrote to memory of 936 4576 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe 83 PID 4576 wrote to memory of 936 4576 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe 83 PID 4576 wrote to memory of 936 4576 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe 83 PID 4576 wrote to memory of 936 4576 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe 83 PID 4576 wrote to memory of 936 4576 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe 83 PID 4576 wrote to memory of 936 4576 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe 83 PID 4576 wrote to memory of 936 4576 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe 83 PID 4576 wrote to memory of 936 4576 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe 83 PID 4576 wrote to memory of 936 4576 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe 83 PID 4576 wrote to memory of 936 4576 2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe"C:\Users\Admin\AppData\Local\Temp\2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe"1⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4576 -
C:\Users\Admin\AppData\Local\Temp\2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe"C:\Users\Admin\AppData\Local\Temp\2d8fffddf0347f8523f553499b6b0b3d55f7b5be3630be52e4bb809ceb2b461c.exe" Track="0001001000"2⤵
- Suspicious use of SetWindowsHookEx
PID:936
-