Analysis
-
max time kernel
140s -
max time network
146s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
12-10-2023 06:06
Static task
static1
Behavioral task
behavioral1
Sample
58c2e7a55e59bbac22646f7e3e6436da1ba53d0540b3836a0ca8716b491b4d2f.exe
Resource
win7-20230831-en
windows7-x64
3 signatures
150 seconds
General
-
Target
58c2e7a55e59bbac22646f7e3e6436da1ba53d0540b3836a0ca8716b491b4d2f.exe
-
Size
700KB
-
MD5
d7c47fb963c65bc517512b54cb5e5e6d
-
SHA1
2dee04c2b7df6404a40a18c70d7e9e5266bc0e86
-
SHA256
58c2e7a55e59bbac22646f7e3e6436da1ba53d0540b3836a0ca8716b491b4d2f
-
SHA512
367fc1d3a65cdde75d70cec03a759a28ac82447e67ab00f16c0124dcc0a8c34505919382cadddd4c0ab2ff73c7bbbfaca655c9892af35f99c4bc4155a26f7f83
-
SSDEEP
6144:Y6vPALOgBE8y8wl5zNci/6VucQZFz6O990yu8VZxRJvhWav+8n6gwaPKn6B8Vsr:pgOgxyKVucQZcS9xdZxjZWpgwaM63r
Malware Config
Extracted
Family
mystic
C2
http://5.42.92.211/loghub/master
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3764 set thread context of 1420 3764 58c2e7a55e59bbac22646f7e3e6436da1ba53d0540b3836a0ca8716b491b4d2f.exe 90 -
Program crash 1 IoCs
pid pid_target Process procid_target 1528 3764 WerFault.exe 70 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 3764 wrote to memory of 1420 3764 58c2e7a55e59bbac22646f7e3e6436da1ba53d0540b3836a0ca8716b491b4d2f.exe 90 PID 3764 wrote to memory of 1420 3764 58c2e7a55e59bbac22646f7e3e6436da1ba53d0540b3836a0ca8716b491b4d2f.exe 90 PID 3764 wrote to memory of 1420 3764 58c2e7a55e59bbac22646f7e3e6436da1ba53d0540b3836a0ca8716b491b4d2f.exe 90 PID 3764 wrote to memory of 1420 3764 58c2e7a55e59bbac22646f7e3e6436da1ba53d0540b3836a0ca8716b491b4d2f.exe 90 PID 3764 wrote to memory of 1420 3764 58c2e7a55e59bbac22646f7e3e6436da1ba53d0540b3836a0ca8716b491b4d2f.exe 90 PID 3764 wrote to memory of 1420 3764 58c2e7a55e59bbac22646f7e3e6436da1ba53d0540b3836a0ca8716b491b4d2f.exe 90 PID 3764 wrote to memory of 1420 3764 58c2e7a55e59bbac22646f7e3e6436da1ba53d0540b3836a0ca8716b491b4d2f.exe 90 PID 3764 wrote to memory of 1420 3764 58c2e7a55e59bbac22646f7e3e6436da1ba53d0540b3836a0ca8716b491b4d2f.exe 90 PID 3764 wrote to memory of 1420 3764 58c2e7a55e59bbac22646f7e3e6436da1ba53d0540b3836a0ca8716b491b4d2f.exe 90 PID 3764 wrote to memory of 1420 3764 58c2e7a55e59bbac22646f7e3e6436da1ba53d0540b3836a0ca8716b491b4d2f.exe 90
Processes
-
C:\Users\Admin\AppData\Local\Temp\58c2e7a55e59bbac22646f7e3e6436da1ba53d0540b3836a0ca8716b491b4d2f.exe"C:\Users\Admin\AppData\Local\Temp\58c2e7a55e59bbac22646f7e3e6436da1ba53d0540b3836a0ca8716b491b4d2f.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3764 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1420
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3764 -s 3002⤵
- Program crash
PID:1528
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 448 -p 3764 -ip 37641⤵PID:4620