Analysis
-
max time kernel
132s -
max time network
105s -
platform
windows10-2004_x64 -
resource
win10v2004-20240611-en -
resource tags
arch:x64arch:x86image:win10v2004-20240611-enlocale:en-usos:windows10-2004-x64system -
submitted
30-06-2024 07:52
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe
Resource
win10v2004-20240611-en
windows10-2004-x64
4 signatures
150 seconds
General
-
Target
0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe
-
Size
1.8MB
-
MD5
97768ab0a4837757b74de2ae892badab
-
SHA1
d8bdfdb717b64ee4cd7a892bbddd293f7eaf915c
-
SHA256
0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77
-
SHA512
78bc5c866b12fcc82cdda20622694824b227a4d522632ffca4b6608bb5245a5e39c28e7f10dfd9e253407a922dae47a83171fb3f605597af4f7186c3aaf5dcde
-
SSDEEP
49152:Ktx9fJc02euDyRs7NNvZpFW3wrqirfHWZjlavwpX:Ktx9fe02beG5Nv+w+irHWZjlavwpX
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2552 set thread context of 100 2552 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 88 -
Program crash 1 IoCs
pid pid_target Process procid_target 4416 2552 WerFault.exe 81 -
Suspicious use of WriteProcessMemory 16 IoCs
description pid Process procid_target PID 2552 wrote to memory of 4460 2552 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 86 PID 2552 wrote to memory of 4460 2552 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 86 PID 2552 wrote to memory of 4460 2552 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 86 PID 2552 wrote to memory of 208 2552 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 87 PID 2552 wrote to memory of 208 2552 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 87 PID 2552 wrote to memory of 208 2552 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 87 PID 2552 wrote to memory of 100 2552 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 88 PID 2552 wrote to memory of 100 2552 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 88 PID 2552 wrote to memory of 100 2552 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 88 PID 2552 wrote to memory of 100 2552 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 88 PID 2552 wrote to memory of 100 2552 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 88 PID 2552 wrote to memory of 100 2552 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 88 PID 2552 wrote to memory of 100 2552 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 88 PID 2552 wrote to memory of 100 2552 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 88 PID 2552 wrote to memory of 100 2552 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 88 PID 2552 wrote to memory of 100 2552 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 88
Processes
-
C:\Users\Admin\AppData\Local\Temp\0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe"C:\Users\Admin\AppData\Local\Temp\0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2552 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:4460
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:208
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:100
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2552 -s 3322⤵
- Program crash
PID:4416
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 404 -p 2552 -ip 25521⤵PID:2564