Analysis
-
max time kernel
115s -
max time network
137s -
platform
windows10-1703_x64 -
resource
win10-20230915-en -
resource tags
arch:x64arch:x86image:win10-20230915-enlocale:en-usos:windows10-1703-x64system -
submitted
11-10-2023 01:13
Static task
static1
Behavioral task
behavioral1
Sample
1a7db2e5e001d9e6b4fe54e52bab03fb44ccb17e87988f77f92f76e4b0066e07.exe
Resource
win10-20230915-en
windows10-1703-x64
3 signatures
150 seconds
General
-
Target
1a7db2e5e001d9e6b4fe54e52bab03fb44ccb17e87988f77f92f76e4b0066e07.exe
-
Size
449KB
-
MD5
d0b7f9f5f83fe41b2a9183590fa3a3cb
-
SHA1
8783cf005f62fab3107e70de6cfa311abb3be0b0
-
SHA256
1a7db2e5e001d9e6b4fe54e52bab03fb44ccb17e87988f77f92f76e4b0066e07
-
SHA512
893f7dba31c3d69bfdd9bcdecf30582e8cdbeb9a4ca009094e4df38c2b7abe8c733f19ed1d138b5f9e2c3ffee0738478fcfb0ff3a4d7b138a88951c201916aa9
-
SSDEEP
6144:Ek/I+MmaQ2AFxs0B3bGToETd6zg+AOCe8hAnsWtNqiApi6CvCRka0qHBYGPefjTz:3Q+1a/mxT3CmIqnsWtIpCvA30cuGmfjP
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4656 set thread context of 2612 4656 1a7db2e5e001d9e6b4fe54e52bab03fb44ccb17e87988f77f92f76e4b0066e07.exe 70 -
Program crash 1 IoCs
pid pid_target Process procid_target 1040 4656 WerFault.exe 69 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4656 wrote to memory of 2612 4656 1a7db2e5e001d9e6b4fe54e52bab03fb44ccb17e87988f77f92f76e4b0066e07.exe 70 PID 4656 wrote to memory of 2612 4656 1a7db2e5e001d9e6b4fe54e52bab03fb44ccb17e87988f77f92f76e4b0066e07.exe 70 PID 4656 wrote to memory of 2612 4656 1a7db2e5e001d9e6b4fe54e52bab03fb44ccb17e87988f77f92f76e4b0066e07.exe 70 PID 4656 wrote to memory of 2612 4656 1a7db2e5e001d9e6b4fe54e52bab03fb44ccb17e87988f77f92f76e4b0066e07.exe 70 PID 4656 wrote to memory of 2612 4656 1a7db2e5e001d9e6b4fe54e52bab03fb44ccb17e87988f77f92f76e4b0066e07.exe 70 PID 4656 wrote to memory of 2612 4656 1a7db2e5e001d9e6b4fe54e52bab03fb44ccb17e87988f77f92f76e4b0066e07.exe 70 PID 4656 wrote to memory of 2612 4656 1a7db2e5e001d9e6b4fe54e52bab03fb44ccb17e87988f77f92f76e4b0066e07.exe 70 PID 4656 wrote to memory of 2612 4656 1a7db2e5e001d9e6b4fe54e52bab03fb44ccb17e87988f77f92f76e4b0066e07.exe 70 PID 4656 wrote to memory of 2612 4656 1a7db2e5e001d9e6b4fe54e52bab03fb44ccb17e87988f77f92f76e4b0066e07.exe 70 PID 4656 wrote to memory of 2612 4656 1a7db2e5e001d9e6b4fe54e52bab03fb44ccb17e87988f77f92f76e4b0066e07.exe 70
Processes
-
C:\Users\Admin\AppData\Local\Temp\1a7db2e5e001d9e6b4fe54e52bab03fb44ccb17e87988f77f92f76e4b0066e07.exe"C:\Users\Admin\AppData\Local\Temp\1a7db2e5e001d9e6b4fe54e52bab03fb44ccb17e87988f77f92f76e4b0066e07.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4656 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2612
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4656 -s 3522⤵
- Program crash
PID:1040
-