Analysis
-
max time kernel
149s -
max time network
188s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
06-12-2022 16:38
Static task
static1
Behavioral task
behavioral1
Sample
988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7.exe
Resource
win10v2004-20221111-en
General
-
Target
988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7.exe
-
Size
56KB
-
MD5
c6433cdf79a2b573d05649c861fdce73
-
SHA1
a644b70df44addbc97af3ff508b197b1f2485445
-
SHA256
988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7
-
SHA512
0588890febbcf6ce1baee19ae272ce50aa6e2359dc04def5a4ba100de8f0d2bbbaf58528fce38eb81828ac064c94b7ff798cf13f3033d6cb95a45b03bd416785
-
SSDEEP
768:y+JS71pvXry+vvYgDGoB+Uu0jCJDKV72pa1BLcceUCSSDaXdF+lF7P7J5reaCn+v:poD2aYWvl7v3ccepSY+A37feaCMJDmS
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1660 set thread context of 208 1660 988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7.exe 83 -
Program crash 1 IoCs
pid pid_target Process procid_target 1100 208 WerFault.exe 83 -
Suspicious use of UnmapMainImage 1 IoCs
pid Process 208 988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7.exe -
Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 1660 wrote to memory of 208 1660 988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7.exe 83 PID 1660 wrote to memory of 208 1660 988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7.exe 83 PID 1660 wrote to memory of 208 1660 988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7.exe 83 PID 1660 wrote to memory of 208 1660 988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7.exe 83 PID 1660 wrote to memory of 208 1660 988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7.exe 83 PID 1660 wrote to memory of 208 1660 988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7.exe 83 PID 1660 wrote to memory of 208 1660 988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7.exe 83 PID 1660 wrote to memory of 208 1660 988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7.exe"C:\Users\Admin\AppData\Local\Temp\988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1660 -
C:\Users\Admin\AppData\Local\Temp\988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7.exe"C:\Users\Admin\AppData\Local\Temp\988405deb1c4436935357f0b8d691cf8e98bac3e5ebd04021cb36b521d185eb7.exe"2⤵
- Suspicious use of UnmapMainImage
PID:208 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 208 -s 123⤵
- Program crash
PID:1100
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 420 -p 208 -ip 2081⤵PID:4676