Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
122s -
max time network
131s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
10/10/2023, 22:21
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe
-
Size
356KB
-
MD5
12b455c4175731142ff6eb653193fb23
-
SHA1
475387ae1b3f802f76acc44fb2958930e8a6533d
-
SHA256
3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556
-
SHA512
2622e4bf7f8d4fa2cbd0fc7e683f74e61ad63ce33d88a4c60cf45491b087e5909ef3fd22a247d0476fa72b2a9d7a8bda26ea94757f8f4ef04a30e39328c43583
-
SSDEEP
6144:wMTeW/s5GqrO5aXnfEGIXWPvZAO4y44zVu2Stje2/Eh5rkdY9un44eVs0BC+:wmcGqrOk86xA4s2SEOGs0BC+
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/3056-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3056-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3056-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3056-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3056-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/3056-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2256 set thread context of 3056 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 29 -
Program crash 2 IoCs
pid pid_target Process procid_target 908 2256 WerFault.exe 27 1212 3056 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 2256 wrote to memory of 3056 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 29 PID 2256 wrote to memory of 3056 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 29 PID 2256 wrote to memory of 3056 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 29 PID 2256 wrote to memory of 3056 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 29 PID 2256 wrote to memory of 3056 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 29 PID 2256 wrote to memory of 3056 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 29 PID 2256 wrote to memory of 3056 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 29 PID 2256 wrote to memory of 3056 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 29 PID 2256 wrote to memory of 3056 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 29 PID 2256 wrote to memory of 3056 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 29 PID 2256 wrote to memory of 3056 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 29 PID 2256 wrote to memory of 3056 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 29 PID 2256 wrote to memory of 3056 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 29 PID 2256 wrote to memory of 3056 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 29 PID 2256 wrote to memory of 908 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 30 PID 2256 wrote to memory of 908 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 30 PID 2256 wrote to memory of 908 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 30 PID 2256 wrote to memory of 908 2256 3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe 30 PID 3056 wrote to memory of 1212 3056 AppLaunch.exe 31 PID 3056 wrote to memory of 1212 3056 AppLaunch.exe 31 PID 3056 wrote to memory of 1212 3056 AppLaunch.exe 31 PID 3056 wrote to memory of 1212 3056 AppLaunch.exe 31 PID 3056 wrote to memory of 1212 3056 AppLaunch.exe 31 PID 3056 wrote to memory of 1212 3056 AppLaunch.exe 31 PID 3056 wrote to memory of 1212 3056 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe"C:\Users\Admin\AppData\Local\Temp\3bf82e78c1668578276f0eff8ede9d61d214f78b6d495764c740e0869abcb556.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2256 -
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:3056 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3056 -s 1963⤵
- Program crash
PID:1212
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2256 -s 762⤵
- Program crash
PID:908
-