Analysis
-
max time kernel
91s -
max time network
99s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
23-11-2022 18:41
Static task
static1
Behavioral task
behavioral1
Sample
c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe
Resource
win10v2004-20220901-en
General
-
Target
c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe
-
Size
814KB
-
MD5
34b8d5949cdb29ffe01c3073bcde3acd
-
SHA1
e25364d138b1c751f75025c86679ec388c745983
-
SHA256
c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720
-
SHA512
578a574432dfca2c0f1a63ab9d86d9bea37cb42bb7ca82ec32366ddcef3e0263da6f88d7861f96a7f8a7e4f96237ba05356ec09da8cae52033e194ecdf1b6119
-
SSDEEP
24576:xHgAHgAr6yAXbr8RuO0uku+RvLt4SWFo2QS:xHgAHgAr1A8uKku+RvLt4SWFo2QS
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exedescription pid process target process PID 4252 set thread context of 4264 4252 c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 260 4264 WerFault.exe c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exepid process 4252 c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe -
Suspicious use of WriteProcessMemory 13 IoCs
Processes:
c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exedescription pid process target process PID 4252 wrote to memory of 4264 4252 c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe PID 4252 wrote to memory of 4264 4252 c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe PID 4252 wrote to memory of 4264 4252 c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe PID 4252 wrote to memory of 4264 4252 c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe PID 4252 wrote to memory of 4264 4252 c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe PID 4252 wrote to memory of 4264 4252 c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe PID 4252 wrote to memory of 4264 4252 c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe PID 4252 wrote to memory of 4264 4252 c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe PID 4252 wrote to memory of 4264 4252 c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe PID 4252 wrote to memory of 4264 4252 c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe PID 4252 wrote to memory of 4264 4252 c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe PID 4252 wrote to memory of 4264 4252 c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe PID 4252 wrote to memory of 4264 4252 c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe"C:\Users\Admin\AppData\Local\Temp\c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4252 -
C:\Users\Admin\AppData\Local\Temp\c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe"C:\Users\Admin\AppData\Local\Temp\c8b12cc76c8b272a372e0919b92d16631dcdb53def447095481b61af5c87b720.exe"2⤵PID:4264
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4264 -s 4443⤵
- Program crash
PID:260
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 444 -p 4264 -ip 42641⤵PID:3480