Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
121s -
max time network
125s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
11/10/2023, 10:22
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe
-
Size
350KB
-
MD5
8e18401156039b21c04e08089c40cefe
-
SHA1
7a378fcec369cd304ce2cf5bc98b882d5dc4eac0
-
SHA256
597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182
-
SHA512
61510edd8e27eac3e98e4e2e02059c92cd6e4f3e7f4eecc364a3412b5a606a0930ffcdd8a8c0e2ece14309e084c5db106231f5f52c13406c50741744088aefae
-
SSDEEP
6144:wtHLsrNJmc30jXud9b7zAO2p70n6nR7lNhP4eYG3e7Be472lTaJF4S:wixJm+bz4pwn6nRpkr7s4SQF4S
Malware Config
Extracted
Family
mystic
C2
http://5.42.92.211/loghub/master
Signatures
-
Detect Mystic stealer payload 8 IoCs
resource yara_rule behavioral1/memory/2416-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2416-6-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2416-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2416-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2416-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2416-13-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2416-14-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2416-15-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1600 set thread context of 2416 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 29 -
Program crash 1 IoCs
pid pid_target Process procid_target 1968 1600 WerFault.exe 21 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 1600 wrote to memory of 2224 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 28 PID 1600 wrote to memory of 2224 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 28 PID 1600 wrote to memory of 2224 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 28 PID 1600 wrote to memory of 2224 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 28 PID 1600 wrote to memory of 2224 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 28 PID 1600 wrote to memory of 2224 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 28 PID 1600 wrote to memory of 2224 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 28 PID 1600 wrote to memory of 2416 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 29 PID 1600 wrote to memory of 2416 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 29 PID 1600 wrote to memory of 2416 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 29 PID 1600 wrote to memory of 2416 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 29 PID 1600 wrote to memory of 2416 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 29 PID 1600 wrote to memory of 2416 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 29 PID 1600 wrote to memory of 2416 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 29 PID 1600 wrote to memory of 2416 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 29 PID 1600 wrote to memory of 2416 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 29 PID 1600 wrote to memory of 2416 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 29 PID 1600 wrote to memory of 2416 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 29 PID 1600 wrote to memory of 2416 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 29 PID 1600 wrote to memory of 2416 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 29 PID 1600 wrote to memory of 2416 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 29 PID 1600 wrote to memory of 1968 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 30 PID 1600 wrote to memory of 1968 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 30 PID 1600 wrote to memory of 1968 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 30 PID 1600 wrote to memory of 1968 1600 597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe 30
Processes
-
C:\Users\Admin\AppData\Local\Temp\597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe"C:\Users\Admin\AppData\Local\Temp\597e38b880e16d86f62825b75801d6700020084a466448258928f30d7c5a8182.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1600 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2224
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2416
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1600 -s 1002⤵
- Program crash
PID:1968
-