Analysis
-
max time kernel
294s -
max time network
343s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
23-11-2022 09:47
Static task
static1
Behavioral task
behavioral1
Sample
cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe
Resource
win10v2004-20221111-en
General
-
Target
cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe
-
Size
1.3MB
-
MD5
bd7e79d5cf64bdef527a8d5e7b8c8c4c
-
SHA1
403df2aa7d0383b5c03c9a628305b6785ab187b1
-
SHA256
cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e
-
SHA512
9552bada9017d95dbbb3fe891127bbfb184ff6f04801a616f3fa303e504b3d834fe16ece3d83b31754aa748a3d6d641b01db1957314f0a42364626c56585ba3d
-
SSDEEP
24576:zrKqlGCPcJKwybUDwEZZODYmR9G+gnbkk6XRJfe3DqYO/KpLwFfngWX4VmJPakm:zrKo4ZwCOnYjVmJPaN
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exedescription pid process target process PID 3496 set thread context of 2204 3496 cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe -
Suspicious use of SetWindowsHookEx 3 IoCs
Processes:
cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exepid process 2204 cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe 2204 cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe 2204 cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exedescription pid process target process PID 3496 wrote to memory of 2204 3496 cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe PID 3496 wrote to memory of 2204 3496 cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe PID 3496 wrote to memory of 2204 3496 cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe PID 3496 wrote to memory of 2204 3496 cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe PID 3496 wrote to memory of 2204 3496 cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe PID 3496 wrote to memory of 2204 3496 cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe PID 3496 wrote to memory of 2204 3496 cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe PID 3496 wrote to memory of 2204 3496 cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe PID 3496 wrote to memory of 2204 3496 cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe PID 3496 wrote to memory of 2204 3496 cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe"C:\Users\Admin\AppData\Local\Temp\cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3496 -
C:\Users\Admin\AppData\Local\Temp\cc384cf8f49fcc146f50762dfe129ee3685e02e78ce4ea9ad5575378f6a3db2e.exe
- Suspicious use of SetWindowsHookEx
PID:2204