Analysis
-
max time kernel
117s -
max time network
120s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
18/04/2024, 07:24
Static task
static1
Behavioral task
behavioral1
Sample
391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe
Resource
win10v2004-20240412-en
General
-
Target
391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe
-
Size
363KB
-
MD5
e720940033d0a875c83f019ee7418487
-
SHA1
872728a8b723b37735a5eaeb35516f747b6b4f17
-
SHA256
391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c
-
SHA512
bb6aebe4e825c72460ff6cc6b6ac17a23033e0faff0ff7c8d2d0a6781459ef5044ff482410863b46dc5f683512e602f7a04a17528ee9d8292f24fddabbb31cdf
-
SSDEEP
6144:wORjQKzqpAnLBZzxKnCoPoMiqbk9MKbzZJR7oM79fI7L+ZQe0cczk:7YSnFLKnCoXiqbkusj9jC+QPccY
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2196 set thread context of 2100 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 30 -
Program crash 1 IoCs
pid pid_target Process procid_target 2548 2100 WerFault.exe 30 -
Suspicious use of WriteProcessMemory 32 IoCs
description pid Process procid_target PID 2196 wrote to memory of 2508 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 28 PID 2196 wrote to memory of 2508 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 28 PID 2196 wrote to memory of 2508 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 28 PID 2196 wrote to memory of 2508 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 28 PID 2196 wrote to memory of 2508 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 28 PID 2196 wrote to memory of 2508 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 28 PID 2196 wrote to memory of 2508 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 28 PID 2196 wrote to memory of 3044 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 29 PID 2196 wrote to memory of 3044 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 29 PID 2196 wrote to memory of 3044 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 29 PID 2196 wrote to memory of 3044 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 29 PID 2196 wrote to memory of 3044 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 29 PID 2196 wrote to memory of 3044 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 29 PID 2196 wrote to memory of 3044 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 29 PID 2196 wrote to memory of 2100 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 30 PID 2196 wrote to memory of 2100 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 30 PID 2196 wrote to memory of 2100 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 30 PID 2196 wrote to memory of 2100 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 30 PID 2196 wrote to memory of 2100 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 30 PID 2196 wrote to memory of 2100 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 30 PID 2196 wrote to memory of 2100 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 30 PID 2196 wrote to memory of 2100 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 30 PID 2196 wrote to memory of 2100 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 30 PID 2196 wrote to memory of 2100 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 30 PID 2196 wrote to memory of 2100 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 30 PID 2196 wrote to memory of 2100 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 30 PID 2196 wrote to memory of 2100 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 30 PID 2196 wrote to memory of 2100 2196 391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe 30 PID 2100 wrote to memory of 2548 2100 RegAsm.exe 31 PID 2100 wrote to memory of 2548 2100 RegAsm.exe 31 PID 2100 wrote to memory of 2548 2100 RegAsm.exe 31 PID 2100 wrote to memory of 2548 2100 RegAsm.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe"C:\Users\Admin\AppData\Local\Temp\391da8243c814cb635942aae0339f210f3520fab3360220d3c68cde1438bd83c.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2196 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2508
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:3044
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:2100 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2100 -s 2563⤵
- Program crash
PID:2548
-
-