Analysis
-
max time kernel
195s -
max time network
299s -
platform
windows10-1703_x64 -
resource
win10-20240404-en -
resource tags
arch:x64arch:x86image:win10-20240404-enlocale:en-usos:windows10-1703-x64system -
submitted
04-07-2024 22:31
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe
Resource
win7-20240704-en
windows7-x64
2 signatures
300 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 3460 set thread context of 208 3460 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 75 -
Program crash 1 IoCs
pid pid_target Process procid_target 4200 3460 WerFault.exe 72 -
Suspicious use of WriteProcessMemory 13 IoCs
description pid Process procid_target PID 3460 wrote to memory of 164 3460 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 74 PID 3460 wrote to memory of 164 3460 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 74 PID 3460 wrote to memory of 164 3460 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 74 PID 3460 wrote to memory of 208 3460 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 75 PID 3460 wrote to memory of 208 3460 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 75 PID 3460 wrote to memory of 208 3460 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 75 PID 3460 wrote to memory of 208 3460 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 75 PID 3460 wrote to memory of 208 3460 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 75 PID 3460 wrote to memory of 208 3460 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 75 PID 3460 wrote to memory of 208 3460 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 75 PID 3460 wrote to memory of 208 3460 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 75 PID 3460 wrote to memory of 208 3460 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 75 PID 3460 wrote to memory of 208 3460 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 75
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:3460 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:164
-
-
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\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3460 -s 3282⤵
- Program crash
PID:4200
-