Analysis
-
max time kernel
150s -
max time network
161s -
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, 14:59
Static task
static1
Behavioral task
behavioral1
Sample
2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe
Resource
win10v2004-20220812-en
General
-
Target
2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe
-
Size
1.3MB
-
MD5
1d45607de323e18da4dabd1454b5f32c
-
SHA1
07593fbcfdbeafb3b3ea907160c3a277bc4e3573
-
SHA256
2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04
-
SHA512
3c22d57731fa1ad02ade259dea407a176e3650cfc86a5fe9bb073cf104e6363ff1cf13f7d0e1822d172d0fcfde8c1c24628f1049cde4d441a95bfdaf0bbd5d40
-
SSDEEP
24576:brKqlGCPcJKwybUDwEZZODYmR9G+gnbkk6XRJfe3DqYO/KpLwFfngWX4VmJPakt:brKo4ZwCOnYjVmJPay
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3692 set thread context of 4380 3692 2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe 79 -
Suspicious use of SetWindowsHookEx 5 IoCs
pid Process 4380 2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe 4380 2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe 4380 2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe 4380 2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe 4380 2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 3692 wrote to memory of 4380 3692 2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe 79 PID 3692 wrote to memory of 4380 3692 2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe 79 PID 3692 wrote to memory of 4380 3692 2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe 79 PID 3692 wrote to memory of 4380 3692 2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe 79 PID 3692 wrote to memory of 4380 3692 2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe 79 PID 3692 wrote to memory of 4380 3692 2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe 79 PID 3692 wrote to memory of 4380 3692 2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe 79 PID 3692 wrote to memory of 4380 3692 2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe 79 PID 3692 wrote to memory of 4380 3692 2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe 79 PID 3692 wrote to memory of 4380 3692 2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe 79
Processes
-
C:\Users\Admin\AppData\Local\Temp\2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe"C:\Users\Admin\AppData\Local\Temp\2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3692 -
C:\Users\Admin\AppData\Local\Temp\2dd6f6336ed984aec49f0ec50bae89f9aa678e9a3323ba2e72cbaa8b457d0e04.exe
- Suspicious use of SetWindowsHookEx
PID:4380
-