Analysis
-
max time kernel
73s -
max time network
157s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
27-11-2022 08:17
Static task
static1
Behavioral task
behavioral1
Sample
f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe
Resource
win10v2004-20220812-en
General
-
Target
f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe
-
Size
1.0MB
-
MD5
884df29af48537bdc9e2f20857b09fb1
-
SHA1
650172f92e71473a9cdcb7b3be61b5b1abc47d8a
-
SHA256
f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe
-
SHA512
9fabc24dd542cfbf1db2edd6869a36ef9043d739a47ecd9892eff1b1e6202a54587e9996991d7c853234709e88381d19941148169c2eca46bf831a4d648b0a28
-
SSDEEP
24576:ilafNPaNMDJOpKROZRpulZBVOkeOLimGHCmO+:CaANaRGRpuHetmGimZ
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\VideoBiosVersion f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.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 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3136 set thread context of 4796 3136 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe 79 -
Suspicious use of SetWindowsHookEx 6 IoCs
pid Process 4796 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe 4796 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe 4796 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe 4796 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe 4796 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe 4796 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 3136 wrote to memory of 4796 3136 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe 79 PID 3136 wrote to memory of 4796 3136 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe 79 PID 3136 wrote to memory of 4796 3136 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe 79 PID 3136 wrote to memory of 4796 3136 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe 79 PID 3136 wrote to memory of 4796 3136 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe 79 PID 3136 wrote to memory of 4796 3136 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe 79 PID 3136 wrote to memory of 4796 3136 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe 79 PID 3136 wrote to memory of 4796 3136 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe 79 PID 3136 wrote to memory of 4796 3136 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe 79 PID 3136 wrote to memory of 4796 3136 f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe 79
Processes
-
C:\Users\Admin\AppData\Local\Temp\f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe"C:\Users\Admin\AppData\Local\Temp\f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe"1⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3136 -
C:\Users\Admin\AppData\Local\Temp\f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe"C:\Users\Admin\AppData\Local\Temp\f801d822a7a383d3eba2bab7af1fb001ea1b7cbdb8cd1b32d1764885baa9c1fe.exe" Track="0001001000"2⤵
- Suspicious use of SetWindowsHookEx
PID:4796
-