Analysis
-
max time kernel
144s -
max time network
164s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
submitted
14-06-2022 22:24
Static task
static1
Behavioral task
behavioral1
Sample
2c9097d5e3a4eb534aa21ecce7e37a613c245130ac3a2a62e6ad2a95963f3cfb.exe
Resource
win7-20220414-en
windows7_x64
0 signatures
0 seconds
Behavioral task
behavioral2
Sample
2c9097d5e3a4eb534aa21ecce7e37a613c245130ac3a2a62e6ad2a95963f3cfb.exe
Resource
win10v2004-20220414-en
windows10-2004_x64
0 signatures
0 seconds
General
-
Target
2c9097d5e3a4eb534aa21ecce7e37a613c245130ac3a2a62e6ad2a95963f3cfb.exe
-
Size
1.0MB
-
MD5
0019cf64b75c815bd2a347572a33570c
-
SHA1
514367af1f7f4371ab980a124342d9ab8ff080de
-
SHA256
2c9097d5e3a4eb534aa21ecce7e37a613c245130ac3a2a62e6ad2a95963f3cfb
-
SHA512
80a16b15eda1718eb6041335857c5a0961ceebb8c36f532e4c31429085c8688ec0c226db0f786c4fd7d390c5ac55a52a30ac502a99e4ff34c5bc217a646176af
Score
3/10
Malware Config
Signatures
-
Program crash 2 IoCs
pid pid_target Process procid_target 4920 4820 WerFault.exe 77 3168 4820 WerFault.exe 77 -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 4820 2c9097d5e3a4eb534aa21ecce7e37a613c245130ac3a2a62e6ad2a95963f3cfb.exe 4820 2c9097d5e3a4eb534aa21ecce7e37a613c245130ac3a2a62e6ad2a95963f3cfb.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\2c9097d5e3a4eb534aa21ecce7e37a613c245130ac3a2a62e6ad2a95963f3cfb.exe"C:\Users\Admin\AppData\Local\Temp\2c9097d5e3a4eb534aa21ecce7e37a613c245130ac3a2a62e6ad2a95963f3cfb.exe"1⤵
- Suspicious use of SetWindowsHookEx
PID:4820 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4820 -s 4162⤵
- Program crash
PID:4920
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4820 -s 4122⤵
- Program crash
PID:3168
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 436 -p 4820 -ip 48201⤵PID:5072
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 516 -p 4820 -ip 48201⤵PID:4216