Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
120s -
max time network
125s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
10/10/2023, 21:56
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe
-
Size
356KB
-
MD5
ee34268c1f6bb64acbc91ba24d7dba85
-
SHA1
4b8faf8e4851570331e3fae98745501ea14e8a6a
-
SHA256
a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66
-
SHA512
b44578aecddbd8d3266f633436c59dbacc0554f7c6f5791ae864a11f6d3e38de13780754244834157f7f9e6004d2725de6e2bfb7550df7aaf908b3af3ac9c377
-
SSDEEP
6144:EATeW/s5GqrO5aXnfEGIXWPvZAOZynlZO1zrd4T2scpAuRBqXzE4+WVs0BC+:wmcGqrOk86xKlZNak4B+s0BC+
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/2032-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2032-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2032-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2032-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2032-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2032-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1648 set thread context of 2032 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 29 -
Program crash 2 IoCs
pid pid_target Process procid_target 2392 1648 WerFault.exe 27 2648 2032 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 1648 wrote to memory of 2032 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 29 PID 1648 wrote to memory of 2032 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 29 PID 1648 wrote to memory of 2032 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 29 PID 1648 wrote to memory of 2032 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 29 PID 1648 wrote to memory of 2032 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 29 PID 1648 wrote to memory of 2032 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 29 PID 1648 wrote to memory of 2032 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 29 PID 1648 wrote to memory of 2032 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 29 PID 1648 wrote to memory of 2032 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 29 PID 1648 wrote to memory of 2032 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 29 PID 1648 wrote to memory of 2032 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 29 PID 1648 wrote to memory of 2032 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 29 PID 1648 wrote to memory of 2032 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 29 PID 1648 wrote to memory of 2032 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 29 PID 1648 wrote to memory of 2392 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 30 PID 1648 wrote to memory of 2392 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 30 PID 1648 wrote to memory of 2392 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 30 PID 1648 wrote to memory of 2392 1648 a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe 30 PID 2032 wrote to memory of 2648 2032 AppLaunch.exe 31 PID 2032 wrote to memory of 2648 2032 AppLaunch.exe 31 PID 2032 wrote to memory of 2648 2032 AppLaunch.exe 31 PID 2032 wrote to memory of 2648 2032 AppLaunch.exe 31 PID 2032 wrote to memory of 2648 2032 AppLaunch.exe 31 PID 2032 wrote to memory of 2648 2032 AppLaunch.exe 31 PID 2032 wrote to memory of 2648 2032 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe"C:\Users\Admin\AppData\Local\Temp\a4e0f66c32f30cf5e73c0ceba8b5a90f007f6126594d3475c86094d850761d66.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1648 -
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:2032 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2032 -s 1963⤵
- Program crash
PID:2648
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1648 -s 762⤵
- Program crash
PID:2392
-