Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
119s -
max time network
132s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
12/10/2023, 18:47
Static task
static1
Behavioral task
behavioral1
Sample
1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe
Resource
win7-20230831-en
4 signatures
150 seconds
General
-
Target
1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe
-
Size
371KB
-
MD5
a5833e9c67046bae7ed80ccfbb3a604f
-
SHA1
07242a28d5f1bca9811b2d78d6c6e7bba7e06320
-
SHA256
1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5
-
SHA512
75b66c63ef61be66427307c764f8404ff57016febda2770db8884d17c851cc6e33a5d3bcbd1ce2a6922dd51b8426fa5a82ab6aaa7ef75242ae748fa78c28acc4
-
SSDEEP
6144:/tvJm09zORs+z/TMify9DAOtgQha8dst8S83cx7M+WBIcvn5Ocuy6BC48/:/1w09CK5NsR8KhCI0O7y6Bf8/
Malware Config
Signatures
-
Detect Mystic stealer payload 7 IoCs
resource yara_rule behavioral1/memory/2020-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2020-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2020-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2020-6-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2020-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2020-13-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2020-14-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2480 set thread context of 2020 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 29 -
Suspicious use of WriteProcessMemory 21 IoCs
description pid Process procid_target PID 2480 wrote to memory of 1672 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 28 PID 2480 wrote to memory of 1672 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 28 PID 2480 wrote to memory of 1672 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 28 PID 2480 wrote to memory of 1672 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 28 PID 2480 wrote to memory of 1672 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 28 PID 2480 wrote to memory of 1672 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 28 PID 2480 wrote to memory of 1672 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 28 PID 2480 wrote to memory of 2020 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 29 PID 2480 wrote to memory of 2020 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 29 PID 2480 wrote to memory of 2020 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 29 PID 2480 wrote to memory of 2020 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 29 PID 2480 wrote to memory of 2020 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 29 PID 2480 wrote to memory of 2020 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 29 PID 2480 wrote to memory of 2020 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 29 PID 2480 wrote to memory of 2020 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 29 PID 2480 wrote to memory of 2020 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 29 PID 2480 wrote to memory of 2020 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 29 PID 2480 wrote to memory of 2020 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 29 PID 2480 wrote to memory of 2020 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 29 PID 2480 wrote to memory of 2020 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 29 PID 2480 wrote to memory of 2020 2480 1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe"C:\Users\Admin\AppData\Local\Temp\1704dfde298f138ea36753934950f573a42bc6f00690cfeefc78ab685a422eb5.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2480 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1672
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2020
-