Analysis
-
max time kernel
146s -
max time network
153s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
11/10/2023, 22:55
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
d035a34860a07d51b18749715faac73cd7cfd5f64bd3b3278bca2c200f39fd49.exe
Resource
win7-20230831-en
3 signatures
150 seconds
General
-
Target
d035a34860a07d51b18749715faac73cd7cfd5f64bd3b3278bca2c200f39fd49.exe
-
Size
364KB
-
MD5
b34cc83ce877a741ccfcdcd5276551fc
-
SHA1
e197d7ccbefd15999b41dbd5c1dbde83d7411bed
-
SHA256
d035a34860a07d51b18749715faac73cd7cfd5f64bd3b3278bca2c200f39fd49
-
SHA512
72d54d57af89d64ed1d8900dd40b0cc9f8a6aa2b83c8a47725ba4d36f62d4788687224e64b3b0e6500a3eaf3fc4efd0e86bec58bd33b9015c5770b70c75e8ea4
-
SSDEEP
6144:GM46fuYXChoQTjlFgLuCY1dRuAOi8qKXF71mMbVth5P+nLXj6OYriIh3bnM+O8OK:GVYzXChdTbv1buqLX2OYWIh3bnk8OswX
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 1620 set thread context of 5092 1620 d035a34860a07d51b18749715faac73cd7cfd5f64bd3b3278bca2c200f39fd49.exe 88 -
Program crash 1 IoCs
pid pid_target Process procid_target 4644 1620 WerFault.exe 85 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 1620 wrote to memory of 5092 1620 d035a34860a07d51b18749715faac73cd7cfd5f64bd3b3278bca2c200f39fd49.exe 88 PID 1620 wrote to memory of 5092 1620 d035a34860a07d51b18749715faac73cd7cfd5f64bd3b3278bca2c200f39fd49.exe 88 PID 1620 wrote to memory of 5092 1620 d035a34860a07d51b18749715faac73cd7cfd5f64bd3b3278bca2c200f39fd49.exe 88 PID 1620 wrote to memory of 5092 1620 d035a34860a07d51b18749715faac73cd7cfd5f64bd3b3278bca2c200f39fd49.exe 88 PID 1620 wrote to memory of 5092 1620 d035a34860a07d51b18749715faac73cd7cfd5f64bd3b3278bca2c200f39fd49.exe 88 PID 1620 wrote to memory of 5092 1620 d035a34860a07d51b18749715faac73cd7cfd5f64bd3b3278bca2c200f39fd49.exe 88 PID 1620 wrote to memory of 5092 1620 d035a34860a07d51b18749715faac73cd7cfd5f64bd3b3278bca2c200f39fd49.exe 88 PID 1620 wrote to memory of 5092 1620 d035a34860a07d51b18749715faac73cd7cfd5f64bd3b3278bca2c200f39fd49.exe 88 PID 1620 wrote to memory of 5092 1620 d035a34860a07d51b18749715faac73cd7cfd5f64bd3b3278bca2c200f39fd49.exe 88 PID 1620 wrote to memory of 5092 1620 d035a34860a07d51b18749715faac73cd7cfd5f64bd3b3278bca2c200f39fd49.exe 88
Processes
-
C:\Users\Admin\AppData\Local\Temp\d035a34860a07d51b18749715faac73cd7cfd5f64bd3b3278bca2c200f39fd49.exe"C:\Users\Admin\AppData\Local\Temp\d035a34860a07d51b18749715faac73cd7cfd5f64bd3b3278bca2c200f39fd49.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1620 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:5092
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1620 -s 2602⤵
- Program crash
PID:4644
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 448 -p 1620 -ip 16201⤵PID:748