Analysis
-
max time kernel
188s -
max time network
294s -
platform
windows10-1703_x64 -
resource
win10-20231220-en -
resource tags
arch:x64arch:x86image:win10-20231220-enlocale:en-usos:windows10-1703-x64system -
submitted
01/01/2024, 04:51
Static task
static1
Behavioral task
behavioral1
Sample
351fadc9f1ddd2bd6bd34ceed2353b8211123e057b52c6aeb60a28643d92f137.exe
Resource
win7-20231215-en
Behavioral task
behavioral2
Sample
351fadc9f1ddd2bd6bd34ceed2353b8211123e057b52c6aeb60a28643d92f137.exe
Resource
win10-20231220-en
General
-
Target
351fadc9f1ddd2bd6bd34ceed2353b8211123e057b52c6aeb60a28643d92f137.exe
-
Size
5.2MB
-
MD5
04f93f610df4d1c941ec7f64679e3039
-
SHA1
11a8b38934a55d203fa78f13e9b7d24754baf9dc
-
SHA256
351fadc9f1ddd2bd6bd34ceed2353b8211123e057b52c6aeb60a28643d92f137
-
SHA512
278aa98a5b62e5939150cef08201a7344a95c3428f9e90e45c26dface8198ed6a1dd52ff830ed7e4ddd3fbc162d9e683ec11fd04af62a505ee6feefccc814b4b
-
SSDEEP
49152:8jxUCLBTkbWcYz5rTyMHUORJeiHkcO09cl2xeAEynEOsFDqnNg9QFiDxAdlv+nZq:6UCpkUHUyeiHK2r8FDkNgyFo51C2ARt
Malware Config
Signatures
-
Loads dropped DLL 1 IoCs
pid Process 4040 351fadc9f1ddd2bd6bd34ceed2353b8211123e057b52c6aeb60a28643d92f137.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4040 set thread context of 1368 4040 351fadc9f1ddd2bd6bd34ceed2353b8211123e057b52c6aeb60a28643d92f137.exe 74 -
Program crash 1 IoCs
pid pid_target Process procid_target 1044 1368 WerFault.exe 74 -
Suspicious use of WriteProcessMemory 9 IoCs
description pid Process procid_target PID 4040 wrote to memory of 1368 4040 351fadc9f1ddd2bd6bd34ceed2353b8211123e057b52c6aeb60a28643d92f137.exe 74 PID 4040 wrote to memory of 1368 4040 351fadc9f1ddd2bd6bd34ceed2353b8211123e057b52c6aeb60a28643d92f137.exe 74 PID 4040 wrote to memory of 1368 4040 351fadc9f1ddd2bd6bd34ceed2353b8211123e057b52c6aeb60a28643d92f137.exe 74 PID 4040 wrote to memory of 1368 4040 351fadc9f1ddd2bd6bd34ceed2353b8211123e057b52c6aeb60a28643d92f137.exe 74 PID 4040 wrote to memory of 1368 4040 351fadc9f1ddd2bd6bd34ceed2353b8211123e057b52c6aeb60a28643d92f137.exe 74 PID 4040 wrote to memory of 1368 4040 351fadc9f1ddd2bd6bd34ceed2353b8211123e057b52c6aeb60a28643d92f137.exe 74 PID 4040 wrote to memory of 1368 4040 351fadc9f1ddd2bd6bd34ceed2353b8211123e057b52c6aeb60a28643d92f137.exe 74 PID 4040 wrote to memory of 1368 4040 351fadc9f1ddd2bd6bd34ceed2353b8211123e057b52c6aeb60a28643d92f137.exe 74 PID 4040 wrote to memory of 1368 4040 351fadc9f1ddd2bd6bd34ceed2353b8211123e057b52c6aeb60a28643d92f137.exe 74
Processes
-
C:\Users\Admin\AppData\Local\Temp\351fadc9f1ddd2bd6bd34ceed2353b8211123e057b52c6aeb60a28643d92f137.exe"C:\Users\Admin\AppData\Local\Temp\351fadc9f1ddd2bd6bd34ceed2353b8211123e057b52c6aeb60a28643d92f137.exe"1⤵
- Loads dropped DLL
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4040 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegSvcs.exeC:\Windows\Microsoft.NET\Framework\v4.0.30319\RegSvcs.exe2⤵PID:1368
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1368 -s 6443⤵
- Program crash
PID:1044
-
-