Analysis
-
max time kernel
142s -
max time network
151s -
platform
windows10-2004_x64 -
resource
win10v2004-20240226-en -
resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system -
submitted
02-07-2024 01:04
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe
Resource
win7-20240221-en
windows7-x64
2 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 3248 set thread context of 2724 3248 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 93 -
Program crash 1 IoCs
pid pid_target Process procid_target 2248 3248 WerFault.exe 90 -
Suspicious use of WriteProcessMemory 13 IoCs
description pid Process procid_target PID 3248 wrote to memory of 1772 3248 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 92 PID 3248 wrote to memory of 1772 3248 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 92 PID 3248 wrote to memory of 1772 3248 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 92 PID 3248 wrote to memory of 2724 3248 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 93 PID 3248 wrote to memory of 2724 3248 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 93 PID 3248 wrote to memory of 2724 3248 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 93 PID 3248 wrote to memory of 2724 3248 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 93 PID 3248 wrote to memory of 2724 3248 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 93 PID 3248 wrote to memory of 2724 3248 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 93 PID 3248 wrote to memory of 2724 3248 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 93 PID 3248 wrote to memory of 2724 3248 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 93 PID 3248 wrote to memory of 2724 3248 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 93 PID 3248 wrote to memory of 2724 3248 0f88ea51a56da966d12311a4b20ea3a6c44315e00747a589f19cf535f90ced77.exe 93
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:3248 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:1772
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2724
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3248 -s 3242⤵
- Program crash
PID:2248
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 412 -p 3248 -ip 32481⤵PID:820
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --type=utility --utility-sub-type=asset_store.mojom.AssetStoreService --lang=en-US --service-sandbox-type=asset_store_service --no-appcompat-clear --mojo-platform-channel-handle=4120 --field-trial-handle=2280,i,4114443225282860369,4764091921472631035,262144 --variations-seed-version /prefetch:81⤵PID:2080