Analysis
-
max time kernel
188s -
max time network
219s -
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 19:27
Static task
static1
Behavioral task
behavioral1
Sample
b8d2e06474042a1100affefeea7f773f0e3cef79b3ae0dcdd91b70bf2787ff43.exe
Resource
win7-20230831-en
windows7-x64
5 signatures
150 seconds
General
-
Target
b8d2e06474042a1100affefeea7f773f0e3cef79b3ae0dcdd91b70bf2787ff43.exe
-
Size
364KB
-
MD5
5d9d5a2813ecc735b2d14bf713d1d3d2
-
SHA1
3ace9b76afff0144385f0f3dff38beb8b55e733a
-
SHA256
b8d2e06474042a1100affefeea7f773f0e3cef79b3ae0dcdd91b70bf2787ff43
-
SHA512
a58c183421e91ef47a29ba3826dac3f93b8b85bd8444159c2461a2c50e342ea1f1b25f7be28f72e270ade53c7136dfeccb67075d74c7694f76511d957b3362d3
-
SSDEEP
6144:/VXAxlt3fuPgyxhV5dAOILRScnYqgljBrwpoPGCH:/2xltWTSLR6qgvwQGCH
Malware Config
Extracted
Family
mystic
C2
http://5.42.92.211/loghub/master
Signatures
-
Detect Mystic stealer payload 5 IoCs
resource yara_rule behavioral2/memory/2600-0-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/2600-1-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/2600-2-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/2600-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/2600-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 532 set thread context of 2600 532 b8d2e06474042a1100affefeea7f773f0e3cef79b3ae0dcdd91b70bf2787ff43.exe 84 -
Program crash 1 IoCs
pid pid_target Process procid_target 2412 532 WerFault.exe 37 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 532 wrote to memory of 2600 532 b8d2e06474042a1100affefeea7f773f0e3cef79b3ae0dcdd91b70bf2787ff43.exe 84 PID 532 wrote to memory of 2600 532 b8d2e06474042a1100affefeea7f773f0e3cef79b3ae0dcdd91b70bf2787ff43.exe 84 PID 532 wrote to memory of 2600 532 b8d2e06474042a1100affefeea7f773f0e3cef79b3ae0dcdd91b70bf2787ff43.exe 84 PID 532 wrote to memory of 2600 532 b8d2e06474042a1100affefeea7f773f0e3cef79b3ae0dcdd91b70bf2787ff43.exe 84 PID 532 wrote to memory of 2600 532 b8d2e06474042a1100affefeea7f773f0e3cef79b3ae0dcdd91b70bf2787ff43.exe 84 PID 532 wrote to memory of 2600 532 b8d2e06474042a1100affefeea7f773f0e3cef79b3ae0dcdd91b70bf2787ff43.exe 84 PID 532 wrote to memory of 2600 532 b8d2e06474042a1100affefeea7f773f0e3cef79b3ae0dcdd91b70bf2787ff43.exe 84 PID 532 wrote to memory of 2600 532 b8d2e06474042a1100affefeea7f773f0e3cef79b3ae0dcdd91b70bf2787ff43.exe 84 PID 532 wrote to memory of 2600 532 b8d2e06474042a1100affefeea7f773f0e3cef79b3ae0dcdd91b70bf2787ff43.exe 84 PID 532 wrote to memory of 2600 532 b8d2e06474042a1100affefeea7f773f0e3cef79b3ae0dcdd91b70bf2787ff43.exe 84
Processes
-
C:\Users\Admin\AppData\Local\Temp\b8d2e06474042a1100affefeea7f773f0e3cef79b3ae0dcdd91b70bf2787ff43.exe"C:\Users\Admin\AppData\Local\Temp\b8d2e06474042a1100affefeea7f773f0e3cef79b3ae0dcdd91b70bf2787ff43.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:532 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2600
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 532 -s 2722⤵
- Program crash
PID:2412
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 440 -p 532 -ip 5321⤵PID:3604