Analysis
-
max time kernel
143s -
max time network
147s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
08-10-2023 17:39
Static task
static1
Behavioral task
behavioral1
Sample
8e81c23a7937b52a8af0945c8a7fc1c9d93ab67c81554e68826877338d46e6f8.exe
Resource
win10v2004-20230915-en
windows10-2004-x64
3 signatures
150 seconds
General
-
Target
8e81c23a7937b52a8af0945c8a7fc1c9d93ab67c81554e68826877338d46e6f8.exe
-
Size
423KB
-
MD5
288e0a46bf7e54e7c397db0ca2cc7743
-
SHA1
31f88e5e103417e027e6a9cf9bb85e224046237f
-
SHA256
8e81c23a7937b52a8af0945c8a7fc1c9d93ab67c81554e68826877338d46e6f8
-
SHA512
da9b6da36fb1a6b8ee5ac624f2e381fa3ff8af098dabfe9535f26dd4946f2694f912affa82746100883acff4a5af2d13606a175b09d1a5f8bc23c4f83e3497a1
-
SSDEEP
12288:HDIxf1XFBC2JQCJMzOpm+5fFfMJ01I6UK66HrlS:HDaNVBfNxFfMJ01Z9rlS
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4648 set thread context of 4192 4648 8e81c23a7937b52a8af0945c8a7fc1c9d93ab67c81554e68826877338d46e6f8.exe 87 -
Program crash 1 IoCs
pid pid_target Process procid_target 1152 4648 WerFault.exe 84 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4648 wrote to memory of 4192 4648 8e81c23a7937b52a8af0945c8a7fc1c9d93ab67c81554e68826877338d46e6f8.exe 87 PID 4648 wrote to memory of 4192 4648 8e81c23a7937b52a8af0945c8a7fc1c9d93ab67c81554e68826877338d46e6f8.exe 87 PID 4648 wrote to memory of 4192 4648 8e81c23a7937b52a8af0945c8a7fc1c9d93ab67c81554e68826877338d46e6f8.exe 87 PID 4648 wrote to memory of 4192 4648 8e81c23a7937b52a8af0945c8a7fc1c9d93ab67c81554e68826877338d46e6f8.exe 87 PID 4648 wrote to memory of 4192 4648 8e81c23a7937b52a8af0945c8a7fc1c9d93ab67c81554e68826877338d46e6f8.exe 87 PID 4648 wrote to memory of 4192 4648 8e81c23a7937b52a8af0945c8a7fc1c9d93ab67c81554e68826877338d46e6f8.exe 87 PID 4648 wrote to memory of 4192 4648 8e81c23a7937b52a8af0945c8a7fc1c9d93ab67c81554e68826877338d46e6f8.exe 87 PID 4648 wrote to memory of 4192 4648 8e81c23a7937b52a8af0945c8a7fc1c9d93ab67c81554e68826877338d46e6f8.exe 87 PID 4648 wrote to memory of 4192 4648 8e81c23a7937b52a8af0945c8a7fc1c9d93ab67c81554e68826877338d46e6f8.exe 87 PID 4648 wrote to memory of 4192 4648 8e81c23a7937b52a8af0945c8a7fc1c9d93ab67c81554e68826877338d46e6f8.exe 87
Processes
-
C:\Users\Admin\AppData\Local\Temp\8e81c23a7937b52a8af0945c8a7fc1c9d93ab67c81554e68826877338d46e6f8.exe"C:\Users\Admin\AppData\Local\Temp\8e81c23a7937b52a8af0945c8a7fc1c9d93ab67c81554e68826877338d46e6f8.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4648 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:4192
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4648 -s 3922⤵
- Program crash
PID:1152
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 460 -p 4648 -ip 46481⤵PID:4480