Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
121s -
max time network
124s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
11/10/2023, 11:18
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe
-
Size
346KB
-
MD5
276174b4255e7bc8ae5d626c19761be2
-
SHA1
fad3e08d3a065268a713bab0e46359ffa45f5b60
-
SHA256
ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7
-
SHA512
664f718aaf39cbfc5a1b912754d7ee36de662ef28565e081f91ea85b98acd1790f2d5ddd1694e543da3c9c3cde1b38eb2dcf21854ad33901b692831b039f6023
-
SSDEEP
6144:8WCGljS9PgGzqLHvw1t6mAOpM0Uyyc/umU2nDY22bReuSVaxL3viKC:8W7S9PgGim0T+9UUDY22bdxziKC
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/2416-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2416-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2416-6-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2416-8-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2416-10-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2416-12-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2108 set thread context of 2416 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 29 -
Program crash 2 IoCs
pid pid_target Process procid_target 1824 2108 WerFault.exe 27 2580 2416 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 2108 wrote to memory of 2416 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 29 PID 2108 wrote to memory of 2416 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 29 PID 2108 wrote to memory of 2416 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 29 PID 2108 wrote to memory of 2416 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 29 PID 2108 wrote to memory of 2416 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 29 PID 2108 wrote to memory of 2416 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 29 PID 2108 wrote to memory of 2416 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 29 PID 2108 wrote to memory of 2416 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 29 PID 2108 wrote to memory of 2416 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 29 PID 2108 wrote to memory of 2416 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 29 PID 2108 wrote to memory of 2416 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 29 PID 2108 wrote to memory of 2416 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 29 PID 2108 wrote to memory of 2416 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 29 PID 2108 wrote to memory of 2416 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 29 PID 2108 wrote to memory of 1824 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 30 PID 2108 wrote to memory of 1824 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 30 PID 2108 wrote to memory of 1824 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 30 PID 2108 wrote to memory of 1824 2108 ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe 30 PID 2416 wrote to memory of 2580 2416 AppLaunch.exe 31 PID 2416 wrote to memory of 2580 2416 AppLaunch.exe 31 PID 2416 wrote to memory of 2580 2416 AppLaunch.exe 31 PID 2416 wrote to memory of 2580 2416 AppLaunch.exe 31 PID 2416 wrote to memory of 2580 2416 AppLaunch.exe 31 PID 2416 wrote to memory of 2580 2416 AppLaunch.exe 31 PID 2416 wrote to memory of 2580 2416 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe"C:\Users\Admin\AppData\Local\Temp\ae6404217d9bbe5213a9bc7d8a93d085c6e11190ca533b5bb09cfa346ef831b7.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2108 -
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:2416 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2416 -s 1963⤵
- Program crash
PID:2580
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2108 -s 1202⤵
- Program crash
PID:1824
-