Analysis
-
max time kernel
112s -
max time network
131s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
20/10/2022, 22:29
Static task
static1
Behavioral task
behavioral1
Sample
00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df.exe
Resource
win10v2004-20220812-en
General
-
Target
00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df.exe
-
Size
1.1MB
-
MD5
72931bd597813b2efd22838c34b6c89e
-
SHA1
f5c3e79a38f9043ce2ef6d78115919f28661a4e3
-
SHA256
00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df
-
SHA512
b40c746ada526b669974a967148269698b08e0446ccbfc0deefb82f8437bf4532381a9fa411111f002b3411bc4e8a423a6d712a4f7ede96fdc850b1fd9dc0f91
-
SSDEEP
3072:qB60Gfo0+BEEmTVlTDolOLRWZs1vOavvvvvvvvvvvvvvvuQT77775HiUKrvgG9oP:qB6BbO884
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1952 set thread context of 2056 1952 00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df.exe 81 -
Program crash 1 IoCs
pid pid_target Process procid_target 4628 2056 WerFault.exe 81 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 1952 00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df.exe -
Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 1952 wrote to memory of 2056 1952 00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df.exe 81 PID 1952 wrote to memory of 2056 1952 00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df.exe 81 PID 1952 wrote to memory of 2056 1952 00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df.exe 81 PID 1952 wrote to memory of 2056 1952 00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df.exe 81 PID 1952 wrote to memory of 2056 1952 00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df.exe 81 PID 1952 wrote to memory of 2056 1952 00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df.exe 81 PID 1952 wrote to memory of 2056 1952 00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df.exe 81 PID 1952 wrote to memory of 2056 1952 00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df.exe 81
Processes
-
C:\Users\Admin\AppData\Local\Temp\00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df.exe"C:\Users\Admin\AppData\Local\Temp\00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1952 -
C:\Users\Admin\AppData\Local\Temp\00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df.exeC:\Users\Admin\AppData\Local\Temp\00fe5e87e1d7546942de843811475cef8ad83410db26a9713806ed68af7cc7df.exe2⤵PID:2056
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2056 -s 3803⤵
- Program crash
PID:4628
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 432 -p 2056 -ip 20561⤵PID:3824