Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
131s -
max time network
138s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
10/10/2023, 22:05
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe
-
Size
356KB
-
MD5
a909efc45b653f749a32b604fb69d1c4
-
SHA1
15a3377f579f9b87a598e37e6ae5adad4714a8aa
-
SHA256
4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770
-
SHA512
40483c3aabab72988429bcecc2d39ff179fa6383863fd3d43505357d6ab5f81a3f016fe52bd42f880ae1e042253e93360a0fd7379dea80819704745e4c7630e3
-
SSDEEP
6144:nETeW/s5GqrO5aXnfEGIXWPvZAOKy9c6dMQgLAEoKw7QaJVs0BC+:RmcGqrOk86xTRENSs0BC+
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/232-0-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/232-1-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/232-2-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/232-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral2/memory/232-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4164 set thread context of 232 4164 4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe 86 -
Program crash 1 IoCs
pid pid_target Process procid_target 3984 4164 WerFault.exe 81 -
Suspicious use of WriteProcessMemory 16 IoCs
description pid Process procid_target PID 4164 wrote to memory of 1032 4164 4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe 84 PID 4164 wrote to memory of 1032 4164 4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe 84 PID 4164 wrote to memory of 1032 4164 4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe 84 PID 4164 wrote to memory of 5004 4164 4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe 85 PID 4164 wrote to memory of 5004 4164 4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe 85 PID 4164 wrote to memory of 5004 4164 4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe 85 PID 4164 wrote to memory of 232 4164 4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe 86 PID 4164 wrote to memory of 232 4164 4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe 86 PID 4164 wrote to memory of 232 4164 4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe 86 PID 4164 wrote to memory of 232 4164 4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe 86 PID 4164 wrote to memory of 232 4164 4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe 86 PID 4164 wrote to memory of 232 4164 4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe 86 PID 4164 wrote to memory of 232 4164 4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe 86 PID 4164 wrote to memory of 232 4164 4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe 86 PID 4164 wrote to memory of 232 4164 4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe 86 PID 4164 wrote to memory of 232 4164 4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe 86
Processes
-
C:\Users\Admin\AppData\Local\Temp\4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe"C:\Users\Admin\AppData\Local\Temp\4565723e0c436a5663f3112dd476f3927ed264e844035c591ec42c2b5b33a770.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4164 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1032
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:5004
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:232
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4164 -s 2762⤵
- Program crash
PID:3984
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 440 -p 4164 -ip 41641⤵PID:1060