Analysis
-
max time kernel
143s -
max time network
149s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
05/10/2023, 19:01
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
df02992944b1861d51500e02d955a8b4cc70a0644746c5e26141f9375267925e_JC.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
df02992944b1861d51500e02d955a8b4cc70a0644746c5e26141f9375267925e_JC.exe
-
Size
1.7MB
-
MD5
e83e9b24b5a4f950b7a6af028f0f8420
-
SHA1
c855531c9c1b704b6d3d482013fd919e380a9bb9
-
SHA256
df02992944b1861d51500e02d955a8b4cc70a0644746c5e26141f9375267925e
-
SHA512
351ced83748ccf5f92e87022138eb0bc66dba26af287eff4b615313e9b43c238d852d87a4f020b494d1a05ff91349ab7f2f64f8727ba7b7c1762fb8ac3a3b647
-
SSDEEP
24576:4cxY5A0vimILMPcVJT6gH/A2Z46a9DhvhI8kS5Vpf:4S0vimILMP4V6SAO46a3vRkqVpf
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/804-0-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/804-1-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/804-2-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/804-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/804-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4968 set thread context of 804 4968 df02992944b1861d51500e02d955a8b4cc70a0644746c5e26141f9375267925e_JC.exe 86 -
Program crash 1 IoCs
pid pid_target Process procid_target 4304 4968 WerFault.exe 84 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4968 wrote to memory of 804 4968 df02992944b1861d51500e02d955a8b4cc70a0644746c5e26141f9375267925e_JC.exe 86 PID 4968 wrote to memory of 804 4968 df02992944b1861d51500e02d955a8b4cc70a0644746c5e26141f9375267925e_JC.exe 86 PID 4968 wrote to memory of 804 4968 df02992944b1861d51500e02d955a8b4cc70a0644746c5e26141f9375267925e_JC.exe 86 PID 4968 wrote to memory of 804 4968 df02992944b1861d51500e02d955a8b4cc70a0644746c5e26141f9375267925e_JC.exe 86 PID 4968 wrote to memory of 804 4968 df02992944b1861d51500e02d955a8b4cc70a0644746c5e26141f9375267925e_JC.exe 86 PID 4968 wrote to memory of 804 4968 df02992944b1861d51500e02d955a8b4cc70a0644746c5e26141f9375267925e_JC.exe 86 PID 4968 wrote to memory of 804 4968 df02992944b1861d51500e02d955a8b4cc70a0644746c5e26141f9375267925e_JC.exe 86 PID 4968 wrote to memory of 804 4968 df02992944b1861d51500e02d955a8b4cc70a0644746c5e26141f9375267925e_JC.exe 86 PID 4968 wrote to memory of 804 4968 df02992944b1861d51500e02d955a8b4cc70a0644746c5e26141f9375267925e_JC.exe 86 PID 4968 wrote to memory of 804 4968 df02992944b1861d51500e02d955a8b4cc70a0644746c5e26141f9375267925e_JC.exe 86
Processes
-
C:\Users\Admin\AppData\Local\Temp\df02992944b1861d51500e02d955a8b4cc70a0644746c5e26141f9375267925e_JC.exe"C:\Users\Admin\AppData\Local\Temp\df02992944b1861d51500e02d955a8b4cc70a0644746c5e26141f9375267925e_JC.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4968 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:804
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4968 -s 4082⤵
- Program crash
PID:4304
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 460 -p 4968 -ip 49681⤵PID:5008