Analysis
-
max time kernel
91s -
max time network
153s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
06/11/2022, 13:27
Static task
static1
Behavioral task
behavioral1
Sample
8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614.exe
Resource
win10v2004-20220901-en
General
-
Target
8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614.exe
-
Size
164KB
-
MD5
0db2a986f06bad440033f4bd0ef0a99c
-
SHA1
a8ec46a53931b0b3c71ada849b7d3d647bd417f1
-
SHA256
8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614
-
SHA512
c7f08f58ce31b88b6c63028601aaff46925da9a3c71cd578903cb619a4c56cfc443afab1b1fa9e78e2a86368a40c6ae7559209e80de3ee0ff78ca8d29e601589
-
SSDEEP
1536:rsygB/8BXcTsNKeCQaKSDauDJeVtZ7Nb3rhWQReRIUFt/eFy:NVXcTZeH1SDYNNb3r78IUz/m
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/4196-135-0x0000000000400000-0x0000000000420000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 5060 set thread context of 4196 5060 8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614.exe 82 -
Program crash 1 IoCs
pid pid_target Process procid_target 2436 4196 WerFault.exe 82 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 5060 8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614.exe -
Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 5060 wrote to memory of 4196 5060 8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614.exe 82 PID 5060 wrote to memory of 4196 5060 8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614.exe 82 PID 5060 wrote to memory of 4196 5060 8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614.exe 82 PID 5060 wrote to memory of 4196 5060 8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614.exe 82 PID 5060 wrote to memory of 4196 5060 8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614.exe 82 PID 5060 wrote to memory of 4196 5060 8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614.exe 82 PID 5060 wrote to memory of 4196 5060 8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614.exe 82 PID 5060 wrote to memory of 4196 5060 8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614.exe 82
Processes
-
C:\Users\Admin\AppData\Local\Temp\8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614.exe"C:\Users\Admin\AppData\Local\Temp\8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:5060 -
C:\Users\Admin\AppData\Local\Temp\8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614.exeC:\Users\Admin\AppData\Local\Temp\8761156d485b4f8c2f72de3cc6cf8ce3cb1d36404c295f554d4d501bde61b614.exe2⤵PID:4196
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4196 -s 1803⤵
- Program crash
PID:2436
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 432 -p 4196 -ip 41961⤵PID:2160