Analysis
-
max time kernel
91s -
max time network
95s -
platform
windows11-21h2_x64 -
resource
win11-20240419-en -
resource tags
arch:x64arch:x86image:win11-20240419-enlocale:en-usos:windows11-21h2-x64system -
submitted
27-05-2024 02:10
Static task
static1
Behavioral task
behavioral1
Sample
d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exe
Resource
win10v2004-20240508-en
Behavioral task
behavioral2
Sample
d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exe
Resource
win11-20240419-en
General
-
Target
d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exe
-
Size
1.2MB
-
MD5
0b7e08a8268a6d413a322ff62d389bf9
-
SHA1
e04b849cc01779fe256744ad31562aca833a82c1
-
SHA256
d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65
-
SHA512
3d226673e30bbbc27e0a5a6c64bf81eca475c697486b20141df7975bef97901d4865b88f41937f5e3dd00b437f24f91493f80cb69aa366b7a49cd17b26197ba4
-
SSDEEP
24576:i3KN/uUnwZcPggVmmNp7c/8B2LF8jfjiKriA4BthZ:i3KDwZqggVmmH7F258jfjiKr/4BB
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exedescription pid process target process PID 3908 set thread context of 4672 3908 d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exe RegAsm.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 1700 3908 WerFault.exe d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exe -
Suspicious use of WriteProcessMemory 9 IoCs
Processes:
d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exedescription pid process target process PID 3908 wrote to memory of 4672 3908 d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exe RegAsm.exe PID 3908 wrote to memory of 4672 3908 d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exe RegAsm.exe PID 3908 wrote to memory of 4672 3908 d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exe RegAsm.exe PID 3908 wrote to memory of 4672 3908 d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exe RegAsm.exe PID 3908 wrote to memory of 4672 3908 d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exe RegAsm.exe PID 3908 wrote to memory of 4672 3908 d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exe RegAsm.exe PID 3908 wrote to memory of 4672 3908 d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exe RegAsm.exe PID 3908 wrote to memory of 4672 3908 d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exe RegAsm.exe PID 3908 wrote to memory of 4672 3908 d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exe RegAsm.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exe"C:\Users\Admin\AppData\Local\Temp\d23a10b3ff0c565ea8ee7f54bcded0582e1e621ebad69d4523d6746f6d8e0e65.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3908 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:4672
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3908 -s 2882⤵
- Program crash
PID:1700
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 416 -p 3908 -ip 39081⤵PID:4992