Analysis
-
max time kernel
240s -
max time network
290s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
12-10-2023 04:48
Static task
static1
Behavioral task
behavioral1
Sample
e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe
Resource
win7-20230831-en
windows7-x64
3 signatures
150 seconds
General
-
Target
e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe
-
Size
700KB
-
MD5
5e1333740eb74f236eb7192331698ad7
-
SHA1
69039501fa630bed304595d5accfea9413cce1b2
-
SHA256
e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6
-
SHA512
4a7c7ffa38a67a5576e998ef920525f6057ede43ab6d28b22e8ecbd8ef873c20c695ad14563992ead4bb39037f5d24182dc4dc0c1c4831f00b8c2b6ee67d1f69
-
SSDEEP
6144:h6vGALXgBEIy8wluzNcq/PVucQpxjcTbFNgAhtrdX3wXQ835vfr:sHXgFysVucQpVCbFNlr+Xd3Br
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2680 set thread context of 2668 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 28 -
Program crash 2 IoCs
pid pid_target Process procid_target 2580 2680 WerFault.exe 11 3036 2668 WerFault.exe 28 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 2680 wrote to memory of 2668 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 28 PID 2680 wrote to memory of 2668 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 28 PID 2680 wrote to memory of 2668 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 28 PID 2680 wrote to memory of 2668 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 28 PID 2680 wrote to memory of 2668 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 28 PID 2680 wrote to memory of 2668 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 28 PID 2680 wrote to memory of 2668 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 28 PID 2680 wrote to memory of 2668 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 28 PID 2680 wrote to memory of 2668 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 28 PID 2680 wrote to memory of 2668 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 28 PID 2680 wrote to memory of 2668 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 28 PID 2680 wrote to memory of 2668 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 28 PID 2680 wrote to memory of 2668 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 28 PID 2680 wrote to memory of 2668 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 28 PID 2680 wrote to memory of 2580 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 29 PID 2680 wrote to memory of 2580 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 29 PID 2680 wrote to memory of 2580 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 29 PID 2680 wrote to memory of 2580 2680 e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe 29 PID 2668 wrote to memory of 3036 2668 AppLaunch.exe 30 PID 2668 wrote to memory of 3036 2668 AppLaunch.exe 30 PID 2668 wrote to memory of 3036 2668 AppLaunch.exe 30 PID 2668 wrote to memory of 3036 2668 AppLaunch.exe 30 PID 2668 wrote to memory of 3036 2668 AppLaunch.exe 30 PID 2668 wrote to memory of 3036 2668 AppLaunch.exe 30 PID 2668 wrote to memory of 3036 2668 AppLaunch.exe 30
Processes
-
C:\Users\Admin\AppData\Local\Temp\e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe"C:\Users\Admin\AppData\Local\Temp\e32e242cedf6b497379fe8da97f8a30f400be1c164258a0fa07169bb3dccbcf6.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2680 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:2668 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2668 -s 1963⤵
- Program crash
PID:3036
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2680 -s 922⤵
- Program crash
PID:2580
-