Analysis
-
max time kernel
138s -
max time network
158s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
15/10/2023, 11:51
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
41ddca05cb27055026126ca58217f78c21c081ad7bf5a5dc2f1b7e6a393d88e5.exe
Resource
win10v2004-20230915-en
3 signatures
150 seconds
General
-
Target
41ddca05cb27055026126ca58217f78c21c081ad7bf5a5dc2f1b7e6a393d88e5.exe
-
Size
295KB
-
MD5
ae7ea1985d411719ade38dd6b4201d89
-
SHA1
ea21a293e815c992ef1ea75747e75990f0af1a29
-
SHA256
41ddca05cb27055026126ca58217f78c21c081ad7bf5a5dc2f1b7e6a393d88e5
-
SHA512
2d097ba56e2b71a8fab1d9ef7f9fe4c253270a928bdf3bdf66868a8e3b3d4c8f97866249d746d660226ffe33d4ebaf8a5100ea91268c649eb0f632f5fd312a47
-
SSDEEP
6144:ed/gu3PkiaRnyYxCIk23COLXvoG/ZpVXiAXdJD4TJn:eZgu33Ik2SOkG/ZpFRNJ4TJn
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 208 set thread context of 4404 208 41ddca05cb27055026126ca58217f78c21c081ad7bf5a5dc2f1b7e6a393d88e5.exe 85 -
Program crash 1 IoCs
pid pid_target Process procid_target 1136 208 WerFault.exe 82 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 208 wrote to memory of 4404 208 41ddca05cb27055026126ca58217f78c21c081ad7bf5a5dc2f1b7e6a393d88e5.exe 85 PID 208 wrote to memory of 4404 208 41ddca05cb27055026126ca58217f78c21c081ad7bf5a5dc2f1b7e6a393d88e5.exe 85 PID 208 wrote to memory of 4404 208 41ddca05cb27055026126ca58217f78c21c081ad7bf5a5dc2f1b7e6a393d88e5.exe 85 PID 208 wrote to memory of 4404 208 41ddca05cb27055026126ca58217f78c21c081ad7bf5a5dc2f1b7e6a393d88e5.exe 85 PID 208 wrote to memory of 4404 208 41ddca05cb27055026126ca58217f78c21c081ad7bf5a5dc2f1b7e6a393d88e5.exe 85 PID 208 wrote to memory of 4404 208 41ddca05cb27055026126ca58217f78c21c081ad7bf5a5dc2f1b7e6a393d88e5.exe 85 PID 208 wrote to memory of 4404 208 41ddca05cb27055026126ca58217f78c21c081ad7bf5a5dc2f1b7e6a393d88e5.exe 85 PID 208 wrote to memory of 4404 208 41ddca05cb27055026126ca58217f78c21c081ad7bf5a5dc2f1b7e6a393d88e5.exe 85 PID 208 wrote to memory of 4404 208 41ddca05cb27055026126ca58217f78c21c081ad7bf5a5dc2f1b7e6a393d88e5.exe 85 PID 208 wrote to memory of 4404 208 41ddca05cb27055026126ca58217f78c21c081ad7bf5a5dc2f1b7e6a393d88e5.exe 85
Processes
-
C:\Users\Admin\AppData\Local\Temp\41ddca05cb27055026126ca58217f78c21c081ad7bf5a5dc2f1b7e6a393d88e5.exe"C:\Users\Admin\AppData\Local\Temp\41ddca05cb27055026126ca58217f78c21c081ad7bf5a5dc2f1b7e6a393d88e5.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:208 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:4404
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 208 -s 1402⤵
- Program crash
PID:1136
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 468 -p 208 -ip 2081⤵PID:1956