Analysis
-
max time kernel
152s -
max time network
191s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
25-11-2022 16:02
Static task
static1
Behavioral task
behavioral1
Sample
34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe
Resource
win10v2004-20220812-en
General
-
Target
34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe
-
Size
1.0MB
-
MD5
9fcf38d9bc10fc3245d37a3d29a57747
-
SHA1
13b46509febc98d1eb127dd64dceb5a38c8cb7da
-
SHA256
34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6
-
SHA512
385c0215fdac22a208e9e8c64b01b384f46ba551695a9d9dfa5d42bc41e3605b7f78ce475cdadc294907abfc8e1bae71b32048791bf37892b264d96916eab2ef
-
SSDEEP
24576:/FPX97BbdQstJ2C/iN7F+ClRV95ZAuvjZtD3Y:/FPtVdRtJ7qT7lRv5ZAuvNG
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4660 set thread context of 4676 4660 34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe 80 -
Suspicious use of SetWindowsHookEx 5 IoCs
pid Process 4676 34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe 4676 34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe 4676 34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe 4676 34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe 4676 34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4660 wrote to memory of 4676 4660 34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe 80 PID 4660 wrote to memory of 4676 4660 34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe 80 PID 4660 wrote to memory of 4676 4660 34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe 80 PID 4660 wrote to memory of 4676 4660 34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe 80 PID 4660 wrote to memory of 4676 4660 34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe 80 PID 4660 wrote to memory of 4676 4660 34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe 80 PID 4660 wrote to memory of 4676 4660 34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe 80 PID 4660 wrote to memory of 4676 4660 34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe 80 PID 4660 wrote to memory of 4676 4660 34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe 80 PID 4660 wrote to memory of 4676 4660 34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe 80
Processes
-
C:\Users\Admin\AppData\Local\Temp\34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe"C:\Users\Admin\AppData\Local\Temp\34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4660 -
C:\Users\Admin\AppData\Local\Temp\34c24adb954b843e44849664cfb363b16aef6b5f0168fb8687d9a74d77de83d6.exe
- Suspicious use of SetWindowsHookEx
PID:4676
-