Analysis
-
max time kernel
144s -
max time network
148s -
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, 18:40
Static task
static1
1 signatures
General
-
Target
736bb0e70437a21da3fb8ada164e747a9590f9a5ac2ba25b390fa8e25b58328d.exe
-
Size
1.7MB
-
MD5
b32d9967a0cd26a1042e9c1ee8cda85b
-
SHA1
bf9859b14c250ebc5230fbb1968f0d78a50dc983
-
SHA256
736bb0e70437a21da3fb8ada164e747a9590f9a5ac2ba25b390fa8e25b58328d
-
SHA512
b951ab5bc1540c3d10c4ffb96796ff3722d3341f87d74e30dd79182b1ae655a764855e6dee8982a56ca88fba78761faa9167fead34b38d48d91a295680038c69
-
SSDEEP
24576:nQxY5A0vimILMPcVJT6gH/A2Z46a9DhvhVNYSuiwf:n20vimILMP4V6SAO46a3vhvuVf
Malware Config
Extracted
Family
mystic
C2
http://5.42.92.211/loghub/master
Signatures
-
Detect Mystic stealer payload 5 IoCs
resource yara_rule behavioral1/memory/4968-0-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/4968-1-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/4968-2-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/4968-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/4968-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2000 set thread context of 4968 2000 736bb0e70437a21da3fb8ada164e747a9590f9a5ac2ba25b390fa8e25b58328d.exe 87 -
Program crash 1 IoCs
pid pid_target Process procid_target 828 2000 WerFault.exe 84 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 2000 wrote to memory of 4968 2000 736bb0e70437a21da3fb8ada164e747a9590f9a5ac2ba25b390fa8e25b58328d.exe 87 PID 2000 wrote to memory of 4968 2000 736bb0e70437a21da3fb8ada164e747a9590f9a5ac2ba25b390fa8e25b58328d.exe 87 PID 2000 wrote to memory of 4968 2000 736bb0e70437a21da3fb8ada164e747a9590f9a5ac2ba25b390fa8e25b58328d.exe 87 PID 2000 wrote to memory of 4968 2000 736bb0e70437a21da3fb8ada164e747a9590f9a5ac2ba25b390fa8e25b58328d.exe 87 PID 2000 wrote to memory of 4968 2000 736bb0e70437a21da3fb8ada164e747a9590f9a5ac2ba25b390fa8e25b58328d.exe 87 PID 2000 wrote to memory of 4968 2000 736bb0e70437a21da3fb8ada164e747a9590f9a5ac2ba25b390fa8e25b58328d.exe 87 PID 2000 wrote to memory of 4968 2000 736bb0e70437a21da3fb8ada164e747a9590f9a5ac2ba25b390fa8e25b58328d.exe 87 PID 2000 wrote to memory of 4968 2000 736bb0e70437a21da3fb8ada164e747a9590f9a5ac2ba25b390fa8e25b58328d.exe 87 PID 2000 wrote to memory of 4968 2000 736bb0e70437a21da3fb8ada164e747a9590f9a5ac2ba25b390fa8e25b58328d.exe 87 PID 2000 wrote to memory of 4968 2000 736bb0e70437a21da3fb8ada164e747a9590f9a5ac2ba25b390fa8e25b58328d.exe 87
Processes
-
C:\Users\Admin\AppData\Local\Temp\736bb0e70437a21da3fb8ada164e747a9590f9a5ac2ba25b390fa8e25b58328d.exe"C:\Users\Admin\AppData\Local\Temp\736bb0e70437a21da3fb8ada164e747a9590f9a5ac2ba25b390fa8e25b58328d.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2000 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:4968
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2000 -s 3922⤵
- Program crash
PID:828
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 452 -p 2000 -ip 20001⤵PID:4800