Analysis
-
max time kernel
145s -
max time network
150s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
22/11/2022, 13:35
Static task
static1
Behavioral task
behavioral1
Sample
450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe
Resource
win10v2004-20220812-en
General
-
Target
450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe
-
Size
1.3MB
-
MD5
0ef6c096e0f743b2436f32bac3c3afe1
-
SHA1
c6b8b39e9fb8afeacd22af82464bb2c0b24240b2
-
SHA256
450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b
-
SHA512
9d8c59afedaab7b501c244cd76160aae30a025818c1b7624cfb79af45420f5ac715710c9dfc660fed81388b8d08ed9304375944a4f077f89c46f028762732693
-
SSDEEP
24576:jrKqlGCPcJKwybUDwEZZODYmR9G+gnbkk6XRJfe3DqYO/KpLwFfngWX4VmJPak7:jrKo4ZwCOnYjVmJPaM
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4400 set thread context of 2000 4400 450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe 81 -
Suspicious use of SetWindowsHookEx 5 IoCs
pid Process 2000 450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe 2000 450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe 2000 450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe 2000 450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe 2000 450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4400 wrote to memory of 2000 4400 450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe 81 PID 4400 wrote to memory of 2000 4400 450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe 81 PID 4400 wrote to memory of 2000 4400 450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe 81 PID 4400 wrote to memory of 2000 4400 450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe 81 PID 4400 wrote to memory of 2000 4400 450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe 81 PID 4400 wrote to memory of 2000 4400 450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe 81 PID 4400 wrote to memory of 2000 4400 450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe 81 PID 4400 wrote to memory of 2000 4400 450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe 81 PID 4400 wrote to memory of 2000 4400 450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe 81 PID 4400 wrote to memory of 2000 4400 450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe 81
Processes
-
C:\Users\Admin\AppData\Local\Temp\450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe"C:\Users\Admin\AppData\Local\Temp\450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4400 -
C:\Users\Admin\AppData\Local\Temp\450df7a1946694f5cf4f0335eef2f039f36a810673ad0438a7f30d3d04e76b3b.exe
- Suspicious use of SetWindowsHookEx
PID:2000
-