Analysis
-
max time kernel
190s -
max time network
264s -
platform
windows10-1703_x64 -
resource
win10-20240611-en -
resource tags
arch:x64arch:x86image:win10-20240611-enlocale:en-usos:windows10-1703-x64system -
submitted
27-06-2024 22:50
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.exe
Resource
win7-20240419-en
windows7-x64
2 signatures
300 seconds
General
-
Target
514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.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 32 set thread context of 5028 32 514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.exe 73 -
Program crash 1 IoCs
pid pid_target Process procid_target 3908 32 WerFault.exe 70 -
Suspicious use of WriteProcessMemory 13 IoCs
description pid Process procid_target PID 32 wrote to memory of 1140 32 514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.exe 72 PID 32 wrote to memory of 1140 32 514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.exe 72 PID 32 wrote to memory of 1140 32 514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.exe 72 PID 32 wrote to memory of 5028 32 514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.exe 73 PID 32 wrote to memory of 5028 32 514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.exe 73 PID 32 wrote to memory of 5028 32 514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.exe 73 PID 32 wrote to memory of 5028 32 514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.exe 73 PID 32 wrote to memory of 5028 32 514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.exe 73 PID 32 wrote to memory of 5028 32 514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.exe 73 PID 32 wrote to memory of 5028 32 514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.exe 73 PID 32 wrote to memory of 5028 32 514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.exe 73 PID 32 wrote to memory of 5028 32 514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.exe 73 PID 32 wrote to memory of 5028 32 514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.exe 73
Processes
-
C:\Users\Admin\AppData\Local\Temp\514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.exe"C:\Users\Admin\AppData\Local\Temp\514efbae5faa43878c743c3db36f81c25ab5d6da93b879b6e88e7a63b1b19769.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:32 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:1140
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:5028
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 32 -s 3042⤵
- Program crash
PID:3908
-