Analysis
-
max time kernel
243s -
max time network
333s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
25-11-2022 01:33
Static task
static1
Behavioral task
behavioral1
Sample
3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe
Resource
win10v2004-20221111-en
General
-
Target
3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe
-
Size
1.3MB
-
MD5
2c82810dc2274591bf5aac189e44e1b4
-
SHA1
b8f63217eb73d83ea4f96313ea3666e1ca0cd641
-
SHA256
3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310
-
SHA512
0b794c8de56c0563c950aa7a020f7b00610b73e051aed8f6be91168d3cae2aea7b351419a61c8deb96d6a17f88a37f4bdc359dc30d8302a65822fb3a7e8d43a8
-
SSDEEP
24576:7rKqlGCPcJKwybUDwEZZODYmR9G+gnbkk6XRJfe3DqYO/KpLwFfngWX4VmJPakW:7rKo4ZwCOnYjVmJPah
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exedescription pid process target process PID 4184 set thread context of 3756 4184 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe -
Suspicious use of SetWindowsHookEx 3 IoCs
Processes:
3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exepid process 3756 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe 3756 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe 3756 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exedescription pid process target process PID 4184 wrote to memory of 3756 4184 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe PID 4184 wrote to memory of 3756 4184 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe PID 4184 wrote to memory of 3756 4184 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe PID 4184 wrote to memory of 3756 4184 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe PID 4184 wrote to memory of 3756 4184 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe PID 4184 wrote to memory of 3756 4184 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe PID 4184 wrote to memory of 3756 4184 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe PID 4184 wrote to memory of 3756 4184 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe PID 4184 wrote to memory of 3756 4184 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe PID 4184 wrote to memory of 3756 4184 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe 3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe"C:\Users\Admin\AppData\Local\Temp\3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4184 -
C:\Users\Admin\AppData\Local\Temp\3ca3a8f7372f716ee5e72bf6ffec702ba55d08c3c1e73de6226ba478b75aa310.exe
- Suspicious use of SetWindowsHookEx
PID:3756