Analysis
-
max time kernel
160s -
max time network
167s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
12-10-2023 17:40
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
22765273d05bbfd3a1ab9f1591fbefa50b2ee3f72b1203b93680ba1867527661.exe
Resource
win10v2004-20230915-en
windows10-2004-x64
3 signatures
150 seconds
General
-
Target
22765273d05bbfd3a1ab9f1591fbefa50b2ee3f72b1203b93680ba1867527661.exe
-
Size
1.1MB
-
MD5
a4c1b3227d35d98d90845a91857b9923
-
SHA1
5aa242eb2bc3829590ee96e604d3c76060849fd9
-
SHA256
22765273d05bbfd3a1ab9f1591fbefa50b2ee3f72b1203b93680ba1867527661
-
SHA512
1db445eb64397b267f037da362786a747deb00db779e7acc603d53a2ef12138fd294dfacbf702b0cdc5b298f77ca736f4a1cb2901cca081a7668ef963436093f
-
SSDEEP
12288:JytkE+5+ova1cPJ4DVN59pAveJahNacgDS2uXYDMqJIv5aXYNfd2l:JaknQova2PJ4DVrM0oNacgovhfd
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 5080 set thread context of 3584 5080 22765273d05bbfd3a1ab9f1591fbefa50b2ee3f72b1203b93680ba1867527661.exe 89 -
Program crash 1 IoCs
pid pid_target Process procid_target 4132 5080 WerFault.exe 85 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 5080 wrote to memory of 3584 5080 22765273d05bbfd3a1ab9f1591fbefa50b2ee3f72b1203b93680ba1867527661.exe 89 PID 5080 wrote to memory of 3584 5080 22765273d05bbfd3a1ab9f1591fbefa50b2ee3f72b1203b93680ba1867527661.exe 89 PID 5080 wrote to memory of 3584 5080 22765273d05bbfd3a1ab9f1591fbefa50b2ee3f72b1203b93680ba1867527661.exe 89 PID 5080 wrote to memory of 3584 5080 22765273d05bbfd3a1ab9f1591fbefa50b2ee3f72b1203b93680ba1867527661.exe 89 PID 5080 wrote to memory of 3584 5080 22765273d05bbfd3a1ab9f1591fbefa50b2ee3f72b1203b93680ba1867527661.exe 89 PID 5080 wrote to memory of 3584 5080 22765273d05bbfd3a1ab9f1591fbefa50b2ee3f72b1203b93680ba1867527661.exe 89 PID 5080 wrote to memory of 3584 5080 22765273d05bbfd3a1ab9f1591fbefa50b2ee3f72b1203b93680ba1867527661.exe 89 PID 5080 wrote to memory of 3584 5080 22765273d05bbfd3a1ab9f1591fbefa50b2ee3f72b1203b93680ba1867527661.exe 89 PID 5080 wrote to memory of 3584 5080 22765273d05bbfd3a1ab9f1591fbefa50b2ee3f72b1203b93680ba1867527661.exe 89 PID 5080 wrote to memory of 3584 5080 22765273d05bbfd3a1ab9f1591fbefa50b2ee3f72b1203b93680ba1867527661.exe 89
Processes
-
C:\Users\Admin\AppData\Local\Temp\22765273d05bbfd3a1ab9f1591fbefa50b2ee3f72b1203b93680ba1867527661.exe"C:\Users\Admin\AppData\Local\Temp\22765273d05bbfd3a1ab9f1591fbefa50b2ee3f72b1203b93680ba1867527661.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:5080 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:3584
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 5080 -s 2362⤵
- Program crash
PID:4132
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 460 -p 5080 -ip 50801⤵PID:1104