Analysis
-
max time kernel
281s -
max time network
360s -
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 10:57
Static task
static1
Behavioral task
behavioral1
Sample
a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe
Resource
win10v2004-20221111-en
General
-
Target
a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe
-
Size
1.3MB
-
MD5
9894218d7ba7ef27f28a1db7fc8f939f
-
SHA1
c3371df33ea815dbdb9304f5cb18edd8e773a93a
-
SHA256
a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec
-
SHA512
7e18e1fc7b08ce8fb6a2b7899dfe1593aed2f6861d65357ec0c8d40cc82a0d605e53af1befa3afd1e867050cbe2f84edab4c06c5523eda1fff5a2a6d34840333
-
SSDEEP
24576:jrKqlGCPcJKwybUDwEZZODYmR9G+gnbkk6XRJfe3DqYO/KpLwFfngWX4VmJPakc:jrKo4ZwCOnYjVmJPan
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exedescription pid process target process PID 1008 set thread context of 3484 1008 a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe -
Suspicious use of SetWindowsHookEx 3 IoCs
Processes:
a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exepid process 3484 a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe 3484 a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe 3484 a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exedescription pid process target process PID 1008 wrote to memory of 3484 1008 a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe PID 1008 wrote to memory of 3484 1008 a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe PID 1008 wrote to memory of 3484 1008 a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe PID 1008 wrote to memory of 3484 1008 a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe PID 1008 wrote to memory of 3484 1008 a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe PID 1008 wrote to memory of 3484 1008 a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe PID 1008 wrote to memory of 3484 1008 a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe PID 1008 wrote to memory of 3484 1008 a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe PID 1008 wrote to memory of 3484 1008 a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe PID 1008 wrote to memory of 3484 1008 a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe"C:\Users\Admin\AppData\Local\Temp\a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1008 -
C:\Users\Admin\AppData\Local\Temp\a1f4247d938b748f3d84e844a157ca12cafea04a96d82444f0e51778ca0b59ec.exe
- Suspicious use of SetWindowsHookEx
PID:3484