Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
120s -
max time network
127s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
13/10/2023, 01:48
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe
-
Size
359KB
-
MD5
25db9e0b436aa6b73f3c5059ee0f81a4
-
SHA1
73e8fc1053cda47fc3ef4c1d00a8688563e1d071
-
SHA256
1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f
-
SHA512
9ea494940c31767993211101bf6f745ea51b5ebb5c4a2be75bd381e28ab769a5a33653a31602a65c3df26e0e6b2e9f0a900be1772c3a2ba53580a1fdf9a79488
-
SSDEEP
6144:1JcaGEZt20ZSwbz8+Dxe8kVAO+lpW/AEyYwwLRUDnnnSEh8Ey:1JFzZtT78T0HWYEyLwLRMh8Ey
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/2088-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2088-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2088-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2088-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2088-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2088-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2408 set thread context of 2088 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 30 -
Program crash 1 IoCs
pid pid_target Process procid_target 2732 2088 WerFault.exe 30 -
Suspicious use of WriteProcessMemory 28 IoCs
description pid Process procid_target PID 2408 wrote to memory of 2676 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 29 PID 2408 wrote to memory of 2676 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 29 PID 2408 wrote to memory of 2676 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 29 PID 2408 wrote to memory of 2676 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 29 PID 2408 wrote to memory of 2676 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 29 PID 2408 wrote to memory of 2676 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 29 PID 2408 wrote to memory of 2676 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 29 PID 2408 wrote to memory of 2088 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 30 PID 2408 wrote to memory of 2088 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 30 PID 2408 wrote to memory of 2088 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 30 PID 2408 wrote to memory of 2088 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 30 PID 2408 wrote to memory of 2088 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 30 PID 2408 wrote to memory of 2088 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 30 PID 2408 wrote to memory of 2088 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 30 PID 2408 wrote to memory of 2088 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 30 PID 2408 wrote to memory of 2088 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 30 PID 2408 wrote to memory of 2088 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 30 PID 2408 wrote to memory of 2088 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 30 PID 2408 wrote to memory of 2088 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 30 PID 2408 wrote to memory of 2088 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 30 PID 2408 wrote to memory of 2088 2408 1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe 30 PID 2088 wrote to memory of 2732 2088 AppLaunch.exe 31 PID 2088 wrote to memory of 2732 2088 AppLaunch.exe 31 PID 2088 wrote to memory of 2732 2088 AppLaunch.exe 31 PID 2088 wrote to memory of 2732 2088 AppLaunch.exe 31 PID 2088 wrote to memory of 2732 2088 AppLaunch.exe 31 PID 2088 wrote to memory of 2732 2088 AppLaunch.exe 31 PID 2088 wrote to memory of 2732 2088 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe"C:\Users\Admin\AppData\Local\Temp\1a3c961e8929fc042c6ea241aab6adb31c7d01088f524bb70d74bbdfd07eba8f.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2408 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2676
-
-
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:2088 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2088 -s 1963⤵
- Program crash
PID:2732
-
-