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
05/10/2023, 19:05
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe
-
Size
1.7MB
-
MD5
5586eda00d71e2dbe2a033d34cd38fb1
-
SHA1
b6635a7612f02ddfd6cde13022b413b199c818bd
-
SHA256
e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d
-
SHA512
a83d4f02656cb289e1e03caedbaf96372fc8f8ebb8b98145a1a9108585dd46974cd010fa2638595c939596309cdc3b00fc04060f9bc653c8304f6127b18eb6be
-
SSDEEP
24576:iUxY5A0vimILMPcVJT6gH/A2Z46a9DhvhmP/PNXRFyixJSf:i60vimILMP4V6SAO46a3vK/FR8ixJSf
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/2444-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2444-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2444-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2444-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2444-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2444-13-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2932 set thread context of 2444 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 30 -
Program crash 2 IoCs
pid pid_target Process procid_target 2384 2932 WerFault.exe 28 2116 2444 WerFault.exe 30 -
Suspicious use of WriteProcessMemory 32 IoCs
description pid Process procid_target PID 2932 wrote to memory of 2244 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 29 PID 2932 wrote to memory of 2244 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 29 PID 2932 wrote to memory of 2244 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 29 PID 2932 wrote to memory of 2244 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 29 PID 2932 wrote to memory of 2244 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 29 PID 2932 wrote to memory of 2244 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 29 PID 2932 wrote to memory of 2244 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 29 PID 2932 wrote to memory of 2444 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 30 PID 2932 wrote to memory of 2444 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 30 PID 2932 wrote to memory of 2444 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 30 PID 2932 wrote to memory of 2444 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 30 PID 2932 wrote to memory of 2444 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 30 PID 2932 wrote to memory of 2444 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 30 PID 2932 wrote to memory of 2444 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 30 PID 2932 wrote to memory of 2444 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 30 PID 2932 wrote to memory of 2444 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 30 PID 2932 wrote to memory of 2444 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 30 PID 2932 wrote to memory of 2444 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 30 PID 2932 wrote to memory of 2444 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 30 PID 2932 wrote to memory of 2444 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 30 PID 2932 wrote to memory of 2444 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 30 PID 2932 wrote to memory of 2384 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 31 PID 2932 wrote to memory of 2384 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 31 PID 2932 wrote to memory of 2384 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 31 PID 2932 wrote to memory of 2384 2932 e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe 31 PID 2444 wrote to memory of 2116 2444 AppLaunch.exe 32 PID 2444 wrote to memory of 2116 2444 AppLaunch.exe 32 PID 2444 wrote to memory of 2116 2444 AppLaunch.exe 32 PID 2444 wrote to memory of 2116 2444 AppLaunch.exe 32 PID 2444 wrote to memory of 2116 2444 AppLaunch.exe 32 PID 2444 wrote to memory of 2116 2444 AppLaunch.exe 32 PID 2444 wrote to memory of 2116 2444 AppLaunch.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe"C:\Users\Admin\AppData\Local\Temp\e283b432b4062b3e4aac7bddfd61180488f8343c7d54fa91cee38a204a803f4d_JC.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2932 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2244
-
-
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:2444 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2444 -s 1963⤵
- Program crash
PID:2116
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2932 -s 1442⤵
- Program crash
PID:2384
-