Analysis
-
max time kernel
151s -
max time network
160s -
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, 20:41
Static task
static1
Behavioral task
behavioral1
Sample
920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe
-
Size
380KB
-
MD5
ec938c456ca87e24dbba13972ea7aa0e
-
SHA1
a2e59aaa5ecb57c1dde22e2ba829578ad4091c13
-
SHA256
920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616
-
SHA512
98dd1d35978064cbe0305684bdc92baee9084042a124ecf9c082220b166b73393c4c310916707777d51807cb85521a7ae6d2006295fdabefbbe0018663ed78df
-
SSDEEP
6144:WlPohHX110KwTVSf3pOCq5b6uAOCblcDoK+fS5sVLqPOnnneasCt4qwm:WlPO3110dVaUcu4et+amVgOnnnbsC/wm
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/1048-2-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/1048-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/1048-1-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/1048-0-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/1048-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 780 set thread context of 1048 780 920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe 86 -
Program crash 1 IoCs
pid pid_target Process procid_target 784 780 WerFault.exe 22 -
Suspicious use of WriteProcessMemory 13 IoCs
description pid Process procid_target PID 780 wrote to memory of 4672 780 920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe 84 PID 780 wrote to memory of 4672 780 920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe 84 PID 780 wrote to memory of 4672 780 920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe 84 PID 780 wrote to memory of 1048 780 920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe 86 PID 780 wrote to memory of 1048 780 920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe 86 PID 780 wrote to memory of 1048 780 920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe 86 PID 780 wrote to memory of 1048 780 920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe 86 PID 780 wrote to memory of 1048 780 920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe 86 PID 780 wrote to memory of 1048 780 920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe 86 PID 780 wrote to memory of 1048 780 920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe 86 PID 780 wrote to memory of 1048 780 920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe 86 PID 780 wrote to memory of 1048 780 920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe 86 PID 780 wrote to memory of 1048 780 920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe 86
Processes
-
C:\Users\Admin\AppData\Local\Temp\920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe"C:\Users\Admin\AppData\Local\Temp\920886402815b9b2d439f3fad6f1ee4ed684bdefa4e8abc3f2bf4c0da1702616.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:780 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:4672
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1048
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 780 -s 2402⤵
- Program crash
PID:784
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 444 -p 780 -ip 7801⤵PID:4140