Analysis
-
max time kernel
134s -
max time network
125s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
28-05-2024 01:29
Static task
static1
Behavioral task
behavioral1
Sample
b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exe
Resource
win7-20240419-en
Behavioral task
behavioral2
Sample
b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exe
Resource
win10v2004-20240508-en
General
-
Target
b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exe
-
Size
1.1MB
-
MD5
c6df0f1fdf3b0d52580f6375537a144a
-
SHA1
639e22e5ace59d41e039c8e89131f69bc8da96e7
-
SHA256
b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c
-
SHA512
ce8552ceea68a0c7e6bbef63fcbbe8ce6a2192bb4dfb96c74a93a13a059698fe31e2b42360183649d1dc9cc096441ae741ae98180634d9f588565437a8c1de8d
-
SSDEEP
24576:GAHnh+eWsN3skA4RV1Hom2KXMmHatdwFWWMX/5:hh+ZkldoPK8YatiFWWMh
Malware Config
Signatures
-
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 1416 2168 WerFault.exe b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exe -
Suspicious behavior: MapViewOfSection 1 IoCs
Processes:
b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exepid process 2168 b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exe -
Suspicious use of FindShellTrayWindow 2 IoCs
Processes:
b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exepid process 2168 b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exe 2168 b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exe -
Suspicious use of SendNotifyMessage 2 IoCs
Processes:
b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exepid process 2168 b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exe 2168 b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exe -
Suspicious use of WriteProcessMemory 4 IoCs
Processes:
b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exedescription pid process target process PID 2168 wrote to memory of 2728 2168 b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exe RegSvcs.exe PID 2168 wrote to memory of 2728 2168 b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exe RegSvcs.exe PID 2168 wrote to memory of 2728 2168 b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exe RegSvcs.exe PID 2168 wrote to memory of 2728 2168 b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exe RegSvcs.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exe"C:\Users\Admin\AppData\Local\Temp\b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exe"1⤵
- Suspicious behavior: MapViewOfSection
- Suspicious use of FindShellTrayWindow
- Suspicious use of SendNotifyMessage
- Suspicious use of WriteProcessMemory
PID:2168 -
C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegSvcs.exe"C:\Users\Admin\AppData\Local\Temp\b0ad6f779e4a72a0e75bb48eec11e8b2f270c95078054e9559505efce6a25c8c.exe"2⤵PID:2728
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2168 -s 6962⤵
- Program crash
PID:1416
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 416 -p 2168 -ip 21681⤵PID:3240