Analysis
-
max time kernel
132s -
max time network
149s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
22-11-2022 16:04
Static task
static1
Behavioral task
behavioral1
Sample
1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe
Resource
win10v2004-20221111-en
General
-
Target
1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe
-
Size
1.3MB
-
MD5
b022acbfca7c5cd7c0f9c2f0e56c02be
-
SHA1
e4b89f3a5054f9edde1af584758dc9473a528c8c
-
SHA256
1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f
-
SHA512
298fef856735d207aa5d6691cfd93a09c2d03694ed81560b68052b2cb60223bcb7be5bc7486c6c39a6040c21097f9e60ea4b6d3e732a2f66a8d762c4fcd67ff3
-
SSDEEP
24576:7rKqlGCPcJKwybUDwEZZODYmR9G+gnbkk6XRJfe3DqYO/KpLwFfngWX4VmJPakX:7rKo4ZwCOnYjVmJPaM
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4364 set thread context of 4264 4364 1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe 83 -
Suspicious use of SetWindowsHookEx 5 IoCs
pid Process 4264 1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe 4264 1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe 4264 1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe 4264 1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe 4264 1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4364 wrote to memory of 4264 4364 1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe 83 PID 4364 wrote to memory of 4264 4364 1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe 83 PID 4364 wrote to memory of 4264 4364 1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe 83 PID 4364 wrote to memory of 4264 4364 1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe 83 PID 4364 wrote to memory of 4264 4364 1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe 83 PID 4364 wrote to memory of 4264 4364 1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe 83 PID 4364 wrote to memory of 4264 4364 1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe 83 PID 4364 wrote to memory of 4264 4364 1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe 83 PID 4364 wrote to memory of 4264 4364 1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe 83 PID 4364 wrote to memory of 4264 4364 1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe"C:\Users\Admin\AppData\Local\Temp\1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4364 -
C:\Users\Admin\AppData\Local\Temp\1b67f6608f0289070c3f3346f8da074e42fbeb1adedf378ba375dfa83fb0da7f.exe
- Suspicious use of SetWindowsHookEx
PID:4264
-