Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
117s -
max time network
121s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
11/10/2023, 11:42
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe
Resource
win7-20230831-en
windows7-x64
5 signatures
150 seconds
General
-
Target
0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe
-
Size
346KB
-
MD5
99a66af56145559acf49ad3759d2cedb
-
SHA1
3eca24c7910cdf47ed530334692c9b86bb366b0f
-
SHA256
0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b
-
SHA512
d26c3cc1c0fd59a8a00cb335a7db367c34ed394ce4e7782877b6806faab2e4454c3d1066e0565e7a3c7274e7254d5f0a0560b1e46e0b4bc159760645986ff3d1
-
SSDEEP
6144:qEC8ljS9PgGzqLHvw1t6mAOt5oW8yVxbgs5VUY4LINUABa3viKC:qEVS9PgGimfeW97bd4LLINUABsiKC
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/2760-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2760-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2760-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2760-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2760-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2760-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3068 set thread context of 2760 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 31 -
Program crash 2 IoCs
pid pid_target Process procid_target 2588 3068 WerFault.exe 16 2756 2760 WerFault.exe 31 -
Suspicious use of WriteProcessMemory 39 IoCs
description pid Process procid_target PID 3068 wrote to memory of 1144 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 29 PID 3068 wrote to memory of 1144 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 29 PID 3068 wrote to memory of 1144 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 29 PID 3068 wrote to memory of 1144 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 29 PID 3068 wrote to memory of 1144 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 29 PID 3068 wrote to memory of 1144 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 29 PID 3068 wrote to memory of 1144 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 29 PID 3068 wrote to memory of 2592 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 30 PID 3068 wrote to memory of 2592 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 30 PID 3068 wrote to memory of 2592 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 30 PID 3068 wrote to memory of 2592 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 30 PID 3068 wrote to memory of 2592 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 30 PID 3068 wrote to memory of 2592 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 30 PID 3068 wrote to memory of 2592 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 30 PID 3068 wrote to memory of 2760 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 31 PID 3068 wrote to memory of 2760 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 31 PID 3068 wrote to memory of 2760 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 31 PID 3068 wrote to memory of 2760 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 31 PID 3068 wrote to memory of 2760 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 31 PID 3068 wrote to memory of 2760 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 31 PID 3068 wrote to memory of 2760 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 31 PID 3068 wrote to memory of 2760 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 31 PID 3068 wrote to memory of 2760 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 31 PID 3068 wrote to memory of 2760 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 31 PID 3068 wrote to memory of 2760 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 31 PID 3068 wrote to memory of 2760 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 31 PID 3068 wrote to memory of 2760 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 31 PID 3068 wrote to memory of 2760 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 31 PID 3068 wrote to memory of 2588 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 32 PID 3068 wrote to memory of 2588 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 32 PID 3068 wrote to memory of 2588 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 32 PID 3068 wrote to memory of 2588 3068 0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe 32 PID 2760 wrote to memory of 2756 2760 AppLaunch.exe 33 PID 2760 wrote to memory of 2756 2760 AppLaunch.exe 33 PID 2760 wrote to memory of 2756 2760 AppLaunch.exe 33 PID 2760 wrote to memory of 2756 2760 AppLaunch.exe 33 PID 2760 wrote to memory of 2756 2760 AppLaunch.exe 33 PID 2760 wrote to memory of 2756 2760 AppLaunch.exe 33 PID 2760 wrote to memory of 2756 2760 AppLaunch.exe 33
Processes
-
C:\Users\Admin\AppData\Local\Temp\0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe"C:\Users\Admin\AppData\Local\Temp\0db79daa6a26ef635a291c9d8dd8f17e19d7dc858622a7974972e40ee5d9347b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3068 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1144
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2592
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:2760 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2760 -s 1963⤵
- Program crash
PID:2756
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3068 -s 1402⤵
- Program crash
PID:2588
-