Analysis
-
max time kernel
127s -
max time network
131s -
platform
windows10-1703_x64 -
resource
win10-20230915-en -
resource tags
arch:x64arch:x86image:win10-20230915-enlocale:en-usos:windows10-1703-x64system -
submitted
02/10/2023, 06:15
Static task
static1
General
-
Target
cc5363e78adbc97637ebfa6f5955e1a47d873a7bec7d7808bcea69e3959e4f5b.exe
-
Size
304KB
-
MD5
a63ee088822d26012a8f639aaeeab6fd
-
SHA1
9483335e5b47b2f9adc96c9e26dd73f0548e679c
-
SHA256
cc5363e78adbc97637ebfa6f5955e1a47d873a7bec7d7808bcea69e3959e4f5b
-
SHA512
c8aa44bfa83b591280b70ccfc1ce51e6272ff03866e60e43ae9bf1b7db3bbc63cf3e226406ac8d1d8402315dddd5a0013aadd21939192ae7f34e66771f41b8e9
-
SSDEEP
6144:UB8VqnD2xsILYMOG1PiSt8I4w2ePPw49OKiP654qfWTRX8:URD2xsILYqUSth/2eQ49Ox654q+TRX8
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4964 set thread context of 5008 4964 cc5363e78adbc97637ebfa6f5955e1a47d873a7bec7d7808bcea69e3959e4f5b.exe 72 -
Program crash 1 IoCs
pid pid_target Process procid_target 4584 4964 WerFault.exe 70 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4964 wrote to memory of 5008 4964 cc5363e78adbc97637ebfa6f5955e1a47d873a7bec7d7808bcea69e3959e4f5b.exe 72 PID 4964 wrote to memory of 5008 4964 cc5363e78adbc97637ebfa6f5955e1a47d873a7bec7d7808bcea69e3959e4f5b.exe 72 PID 4964 wrote to memory of 5008 4964 cc5363e78adbc97637ebfa6f5955e1a47d873a7bec7d7808bcea69e3959e4f5b.exe 72 PID 4964 wrote to memory of 5008 4964 cc5363e78adbc97637ebfa6f5955e1a47d873a7bec7d7808bcea69e3959e4f5b.exe 72 PID 4964 wrote to memory of 5008 4964 cc5363e78adbc97637ebfa6f5955e1a47d873a7bec7d7808bcea69e3959e4f5b.exe 72 PID 4964 wrote to memory of 5008 4964 cc5363e78adbc97637ebfa6f5955e1a47d873a7bec7d7808bcea69e3959e4f5b.exe 72 PID 4964 wrote to memory of 5008 4964 cc5363e78adbc97637ebfa6f5955e1a47d873a7bec7d7808bcea69e3959e4f5b.exe 72 PID 4964 wrote to memory of 5008 4964 cc5363e78adbc97637ebfa6f5955e1a47d873a7bec7d7808bcea69e3959e4f5b.exe 72 PID 4964 wrote to memory of 5008 4964 cc5363e78adbc97637ebfa6f5955e1a47d873a7bec7d7808bcea69e3959e4f5b.exe 72 PID 4964 wrote to memory of 5008 4964 cc5363e78adbc97637ebfa6f5955e1a47d873a7bec7d7808bcea69e3959e4f5b.exe 72
Processes
-
C:\Users\Admin\AppData\Local\Temp\cc5363e78adbc97637ebfa6f5955e1a47d873a7bec7d7808bcea69e3959e4f5b.exe"C:\Users\Admin\AppData\Local\Temp\cc5363e78adbc97637ebfa6f5955e1a47d873a7bec7d7808bcea69e3959e4f5b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4964 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:5008
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4964 -s 1562⤵
- Program crash
PID:4584
-