Analysis
-
max time kernel
141s -
max time network
124s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
05-03-2024 13:48
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
b4d8e7d22fe95b14fc79a1068fdf66f2.exe
Resource
win7-20240221-en
windows7-x64
4 signatures
150 seconds
Behavioral task
behavioral2
Sample
b4d8e7d22fe95b14fc79a1068fdf66f2.exe
Resource
win10v2004-20240226-en
windows10-2004-x64
7 signatures
150 seconds
General
-
Target
b4d8e7d22fe95b14fc79a1068fdf66f2.exe
-
Size
599KB
-
MD5
b4d8e7d22fe95b14fc79a1068fdf66f2
-
SHA1
599937e533c6570a507cd2e96f3a2bda5e72902a
-
SHA256
77e8465236439d398d65d41906b7173559700950c220af0c0db54d168b92b590
-
SHA512
ce665450871c7917cc5d578432371f79a2461f7b0010f4f4df3d2745c0fa9e7740d52bbe772c837637735cb0a2e13f9736c9249533d9d57b712fd74a10f92b24
-
SSDEEP
12288:SfpL7a07Au24ZxQAykcTo9K6ld2D9ccQBb6LS/riACotAViE:QPRAP4j0iIWv5WACoKQE
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3032 set thread context of 2676 3032 b4d8e7d22fe95b14fc79a1068fdf66f2.exe 28 -
Program crash 1 IoCs
pid pid_target Process procid_target 2604 2676 WerFault.exe 28 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 3032 b4d8e7d22fe95b14fc79a1068fdf66f2.exe -
Suspicious use of WriteProcessMemory 13 IoCs
description pid Process procid_target PID 3032 wrote to memory of 2676 3032 b4d8e7d22fe95b14fc79a1068fdf66f2.exe 28 PID 3032 wrote to memory of 2676 3032 b4d8e7d22fe95b14fc79a1068fdf66f2.exe 28 PID 3032 wrote to memory of 2676 3032 b4d8e7d22fe95b14fc79a1068fdf66f2.exe 28 PID 3032 wrote to memory of 2676 3032 b4d8e7d22fe95b14fc79a1068fdf66f2.exe 28 PID 3032 wrote to memory of 2676 3032 b4d8e7d22fe95b14fc79a1068fdf66f2.exe 28 PID 3032 wrote to memory of 2676 3032 b4d8e7d22fe95b14fc79a1068fdf66f2.exe 28 PID 3032 wrote to memory of 2676 3032 b4d8e7d22fe95b14fc79a1068fdf66f2.exe 28 PID 3032 wrote to memory of 2676 3032 b4d8e7d22fe95b14fc79a1068fdf66f2.exe 28 PID 3032 wrote to memory of 2676 3032 b4d8e7d22fe95b14fc79a1068fdf66f2.exe 28 PID 2676 wrote to memory of 2604 2676 b4d8e7d22fe95b14fc79a1068fdf66f2.exe 29 PID 2676 wrote to memory of 2604 2676 b4d8e7d22fe95b14fc79a1068fdf66f2.exe 29 PID 2676 wrote to memory of 2604 2676 b4d8e7d22fe95b14fc79a1068fdf66f2.exe 29 PID 2676 wrote to memory of 2604 2676 b4d8e7d22fe95b14fc79a1068fdf66f2.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\b4d8e7d22fe95b14fc79a1068fdf66f2.exe"C:\Users\Admin\AppData\Local\Temp\b4d8e7d22fe95b14fc79a1068fdf66f2.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3032 -
C:\Users\Admin\AppData\Local\Temp\b4d8e7d22fe95b14fc79a1068fdf66f2.exeC:\Users\Admin\AppData\Local\Temp\b4d8e7d22fe95b14fc79a1068fdf66f2.exe2⤵
- Suspicious use of WriteProcessMemory
PID:2676 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2676 -s 1283⤵
- Program crash
PID:2604
-
-