Analysis
-
max time kernel
147s -
max time network
152s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
06-10-2023 18:58
Static task
static1
General
-
Target
c1617e7a8eda2b696904531107eb3efd5c6be52d40d69e5ad173eb06cd7fecfc.exe
-
Size
378KB
-
MD5
e69c020febac575491a27488995a2cbf
-
SHA1
ed0514e091ae1460940a2eea91968f3feba48910
-
SHA256
c1617e7a8eda2b696904531107eb3efd5c6be52d40d69e5ad173eb06cd7fecfc
-
SHA512
77fc1d2ba5af849a32504dfa795ac75e86ff07c9b6b4edaa5afeeddd2e8e63c296b2c546a67fbc8cb8828125a63bfbded1964f2c81b4a0ca4bc0a38f30086b61
-
SSDEEP
6144:GhCmCH557yGY/fjBximSLB5aAODimxnt5Pitq+eDJYhkRFtNj:Gh0Hr7yV3OW0Wn/l+zkRpj
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/4536-0-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/4536-1-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/4536-2-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/4536-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/4536-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 380 set thread context of 4536 380 c1617e7a8eda2b696904531107eb3efd5c6be52d40d69e5ad173eb06cd7fecfc.exe 87 -
Program crash 1 IoCs
pid pid_target Process procid_target 448 380 WerFault.exe 84 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 380 wrote to memory of 4536 380 c1617e7a8eda2b696904531107eb3efd5c6be52d40d69e5ad173eb06cd7fecfc.exe 87 PID 380 wrote to memory of 4536 380 c1617e7a8eda2b696904531107eb3efd5c6be52d40d69e5ad173eb06cd7fecfc.exe 87 PID 380 wrote to memory of 4536 380 c1617e7a8eda2b696904531107eb3efd5c6be52d40d69e5ad173eb06cd7fecfc.exe 87 PID 380 wrote to memory of 4536 380 c1617e7a8eda2b696904531107eb3efd5c6be52d40d69e5ad173eb06cd7fecfc.exe 87 PID 380 wrote to memory of 4536 380 c1617e7a8eda2b696904531107eb3efd5c6be52d40d69e5ad173eb06cd7fecfc.exe 87 PID 380 wrote to memory of 4536 380 c1617e7a8eda2b696904531107eb3efd5c6be52d40d69e5ad173eb06cd7fecfc.exe 87 PID 380 wrote to memory of 4536 380 c1617e7a8eda2b696904531107eb3efd5c6be52d40d69e5ad173eb06cd7fecfc.exe 87 PID 380 wrote to memory of 4536 380 c1617e7a8eda2b696904531107eb3efd5c6be52d40d69e5ad173eb06cd7fecfc.exe 87 PID 380 wrote to memory of 4536 380 c1617e7a8eda2b696904531107eb3efd5c6be52d40d69e5ad173eb06cd7fecfc.exe 87 PID 380 wrote to memory of 4536 380 c1617e7a8eda2b696904531107eb3efd5c6be52d40d69e5ad173eb06cd7fecfc.exe 87
Processes
-
C:\Users\Admin\AppData\Local\Temp\c1617e7a8eda2b696904531107eb3efd5c6be52d40d69e5ad173eb06cd7fecfc.exe"C:\Users\Admin\AppData\Local\Temp\c1617e7a8eda2b696904531107eb3efd5c6be52d40d69e5ad173eb06cd7fecfc.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:380 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:4536
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 380 -s 1522⤵
- Program crash
PID:448
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 444 -p 380 -ip 3801⤵PID:988