Analysis
-
max time kernel
140s -
max time network
149s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
03-10-2022 02:35
Static task
static1
Behavioral task
behavioral1
Sample
d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3.exe
Resource
win10v2004-20220812-en
General
-
Target
d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3.exe
-
Size
104KB
-
MD5
6c4625c274486a2af1a568e15076eb28
-
SHA1
b5700d0bb57d4f2f39b99092ff3de4baac3335ae
-
SHA256
d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3
-
SHA512
d24f15710378ff1dbf0065722ef12b373c8059d744eaea06d4f81d5c2e98232404ea664424b041b7f1487f0af3948d03492897fde3f219bd01bf9c7e6a2f8e64
-
SSDEEP
1536:ZP7LRKwFKi/fLR2dpCLg8UTIksNThP46/nSM7gQZPYD6qt9:JodMl2dpGSFormQqD6u9
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2524 set thread context of 4668 2524 d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3.exe 81 -
Program crash 1 IoCs
pid pid_target Process procid_target 1696 4668 WerFault.exe 81 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 2524 d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3.exe -
Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 2524 wrote to memory of 4668 2524 d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3.exe 81 PID 2524 wrote to memory of 4668 2524 d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3.exe 81 PID 2524 wrote to memory of 4668 2524 d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3.exe 81 PID 2524 wrote to memory of 4668 2524 d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3.exe 81 PID 2524 wrote to memory of 4668 2524 d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3.exe 81 PID 2524 wrote to memory of 4668 2524 d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3.exe 81 PID 2524 wrote to memory of 4668 2524 d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3.exe 81 PID 2524 wrote to memory of 4668 2524 d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3.exe 81
Processes
-
C:\Users\Admin\AppData\Local\Temp\d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3.exe"C:\Users\Admin\AppData\Local\Temp\d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2524 -
C:\Users\Admin\AppData\Local\Temp\d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3.exeC:\Users\Admin\AppData\Local\Temp\d275f75fd816a5635795897e9af20bec1753fc6a98e3b30b9d4efbdf24a053c3.exe2⤵PID:4668
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4668 -s 2363⤵
- Program crash
PID:1696
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 4668 -ip 46681⤵PID:4988