Analysis
-
max time kernel
143s -
max time network
151s -
platform
windows10-2004_x64 -
resource
win10v2004-20231215-en -
resource tags
arch:x64arch:x86image:win10v2004-20231215-enlocale:en-usos:windows10-2004-x64system -
submitted
30-12-2023 10:21
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
15c0c2ce25e4f02d026c60b6dc58b166.exe
Resource
win7-20231215-en
windows7-x64
6 signatures
150 seconds
Behavioral task
behavioral2
Sample
15c0c2ce25e4f02d026c60b6dc58b166.exe
Resource
win10v2004-20231215-en
windows10-2004-x64
5 signatures
150 seconds
General
-
Target
15c0c2ce25e4f02d026c60b6dc58b166.exe
-
Size
344KB
-
MD5
15c0c2ce25e4f02d026c60b6dc58b166
-
SHA1
2164a4b678d6bbc8a7948a623da40c42f3d10309
-
SHA256
4c5ae07738e2ddf31f25f1244551f1dfe36c571fa1b93470a3fd6befb1a57bb8
-
SHA512
5820add84401e41961d7e8ea33bb2c2b21be4894f242b3309e5825d319edbdc6683a9448f09f5091e210cd2e02e38e3025bcacb1a1dcae0136f234d825ca09bb
-
SSDEEP
3072:X99UZTQXyZYrG7mEKx/tnq3YuVFr3jW8v6fxVQYGXTBmANksb7c9Xtr3hvB99BFO:p8vExOjjVc9XtrtcIFW
Score
7/10
Malware Config
Signatures
-
Executes dropped EXE 1 IoCs
pid Process 628 852E.tmp -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4212 set thread context of 2168 4212 15c0c2ce25e4f02d026c60b6dc58b166.exe 94 -
Program crash 3 IoCs
pid pid_target Process procid_target 1140 628 WerFault.exe 91 1368 2168 WerFault.exe 94 456 2168 WerFault.exe 94 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 4212 15c0c2ce25e4f02d026c60b6dc58b166.exe -
Suspicious use of WriteProcessMemory 14 IoCs
description pid Process procid_target PID 4212 wrote to memory of 2168 4212 15c0c2ce25e4f02d026c60b6dc58b166.exe 94 PID 4212 wrote to memory of 2168 4212 15c0c2ce25e4f02d026c60b6dc58b166.exe 94 PID 4212 wrote to memory of 2168 4212 15c0c2ce25e4f02d026c60b6dc58b166.exe 94 PID 4212 wrote to memory of 2168 4212 15c0c2ce25e4f02d026c60b6dc58b166.exe 94 PID 4212 wrote to memory of 2168 4212 15c0c2ce25e4f02d026c60b6dc58b166.exe 94 PID 4212 wrote to memory of 2168 4212 15c0c2ce25e4f02d026c60b6dc58b166.exe 94 PID 4212 wrote to memory of 2168 4212 15c0c2ce25e4f02d026c60b6dc58b166.exe 94 PID 4212 wrote to memory of 2168 4212 15c0c2ce25e4f02d026c60b6dc58b166.exe 94 PID 4212 wrote to memory of 2168 4212 15c0c2ce25e4f02d026c60b6dc58b166.exe 94 PID 4212 wrote to memory of 2168 4212 15c0c2ce25e4f02d026c60b6dc58b166.exe 94 PID 4212 wrote to memory of 2168 4212 15c0c2ce25e4f02d026c60b6dc58b166.exe 94 PID 2168 wrote to memory of 628 2168 15c0c2ce25e4f02d026c60b6dc58b166.exe 91 PID 2168 wrote to memory of 628 2168 15c0c2ce25e4f02d026c60b6dc58b166.exe 91 PID 2168 wrote to memory of 628 2168 15c0c2ce25e4f02d026c60b6dc58b166.exe 91
Processes
-
C:\Users\Admin\AppData\Local\Temp\15c0c2ce25e4f02d026c60b6dc58b166.exe"C:\Users\Admin\AppData\Local\Temp\15c0c2ce25e4f02d026c60b6dc58b166.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4212 -
C:\Users\Admin\AppData\Local\Temp\15c0c2ce25e4f02d026c60b6dc58b166.exeC:\Users\Admin\AppData\Local\Temp\15c0c2ce25e4f02d026c60b6dc58b166.exe2⤵
- Suspicious use of WriteProcessMemory
PID:2168 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2168 -s 2483⤵
- Program crash
PID:1368
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2168 -s 2563⤵
- Program crash
PID:456
-
-
-
C:\Users\Admin\AppData\Local\Temp\852E.tmpC:\Users\Admin\AppData\Local\Temp\852E.tmp1⤵
- Executes dropped EXE
PID:628 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 628 -s 4882⤵
- Program crash
PID:1140
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 456 -p 2168 -ip 21681⤵PID:3868
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 420 -p 628 -ip 6281⤵PID:3168
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 576 -p 2168 -ip 21681⤵PID:4652