Analysis
-
max time kernel
51s -
max time network
51s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
25-06-2024 16:12
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
c6c9f27d335d4e47b5ea12653e806be6.exe
Resource
win7-20240221-en
windows7-x64
2 signatures
150 seconds
General
-
Target
c6c9f27d335d4e47b5ea12653e806be6.exe
-
Size
1.8MB
-
MD5
c6c9f27d335d4e47b5ea12653e806be6
-
SHA1
e53242d463e2c94383ec646e7e04504b96b4d176
-
SHA256
514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769
-
SHA512
7e00bdac39c89821b776dda372693d29e0e7188f8ef747037b971461af79545908f8fc8c9bbf7a30f1b0cc4ceea45632e91c1093e784002994808c19bd2a7347
-
SSDEEP
49152:KWPLwXMkW4itwCBDtixjSzceiLYtV25Mm8eEMMd:tPLPkW4IwcOj6iLYtV+Mw8
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1228 set thread context of 4752 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 85 -
Program crash 1 IoCs
pid pid_target Process procid_target 5116 1228 WerFault.exe 80 -
Suspicious use of WriteProcessMemory 19 IoCs
description pid Process procid_target PID 1228 wrote to memory of 2696 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 82 PID 1228 wrote to memory of 2696 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 82 PID 1228 wrote to memory of 2696 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 82 PID 1228 wrote to memory of 4944 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 83 PID 1228 wrote to memory of 4944 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 83 PID 1228 wrote to memory of 4944 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 83 PID 1228 wrote to memory of 3148 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 84 PID 1228 wrote to memory of 3148 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 84 PID 1228 wrote to memory of 3148 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 84 PID 1228 wrote to memory of 4752 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 85 PID 1228 wrote to memory of 4752 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 85 PID 1228 wrote to memory of 4752 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 85 PID 1228 wrote to memory of 4752 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 85 PID 1228 wrote to memory of 4752 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 85 PID 1228 wrote to memory of 4752 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 85 PID 1228 wrote to memory of 4752 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 85 PID 1228 wrote to memory of 4752 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 85 PID 1228 wrote to memory of 4752 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 85 PID 1228 wrote to memory of 4752 1228 c6c9f27d335d4e47b5ea12653e806be6.exe 85
Processes
-
C:\Users\Admin\AppData\Local\Temp\c6c9f27d335d4e47b5ea12653e806be6.exe"C:\Users\Admin\AppData\Local\Temp\c6c9f27d335d4e47b5ea12653e806be6.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1228 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2696
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:4944
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:3148
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:4752
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1228 -s 3202⤵
- Program crash
PID:5116
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 1228 -ip 12281⤵PID:4600