Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
120s -
max time network
136s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
11/10/2023, 13:01
Static task
static1
Behavioral task
behavioral1
Sample
9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe
-
Size
379KB
-
MD5
82320cce4237ee3908bdfc9af6f1e9ce
-
SHA1
6af4625450ebae17d87e5d05c5671bf0649f3c49
-
SHA256
9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e
-
SHA512
6983d57e1b52f70e7eaf3175c5a43d50028deefe9dddde25b4f063fa5fc87b80a40a188c189aefa17e2b4688c6593df5c06f5f33249a22f9397ac270c2c87dea
-
SSDEEP
6144:Ol4cRgs3r9vIum2Tg0N63KAOU7/rdu1rJAZuER2WfwTtg3F:OlvRP3r9HmeqbreJiuEFwTC3F
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/1264-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/1264-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/1264-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/1264-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/1264-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/1264-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2448 set thread context of 1264 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 28 -
Program crash 2 IoCs
pid pid_target Process procid_target 2432 2448 WerFault.exe 18 2672 1264 WerFault.exe 28 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 2448 wrote to memory of 1264 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 28 PID 2448 wrote to memory of 1264 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 28 PID 2448 wrote to memory of 1264 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 28 PID 2448 wrote to memory of 1264 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 28 PID 2448 wrote to memory of 1264 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 28 PID 2448 wrote to memory of 1264 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 28 PID 2448 wrote to memory of 1264 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 28 PID 2448 wrote to memory of 1264 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 28 PID 2448 wrote to memory of 1264 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 28 PID 2448 wrote to memory of 1264 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 28 PID 2448 wrote to memory of 1264 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 28 PID 2448 wrote to memory of 1264 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 28 PID 2448 wrote to memory of 1264 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 28 PID 2448 wrote to memory of 1264 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 28 PID 2448 wrote to memory of 2432 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 29 PID 2448 wrote to memory of 2432 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 29 PID 2448 wrote to memory of 2432 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 29 PID 2448 wrote to memory of 2432 2448 9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe 29 PID 1264 wrote to memory of 2672 1264 AppLaunch.exe 30 PID 1264 wrote to memory of 2672 1264 AppLaunch.exe 30 PID 1264 wrote to memory of 2672 1264 AppLaunch.exe 30 PID 1264 wrote to memory of 2672 1264 AppLaunch.exe 30 PID 1264 wrote to memory of 2672 1264 AppLaunch.exe 30 PID 1264 wrote to memory of 2672 1264 AppLaunch.exe 30 PID 1264 wrote to memory of 2672 1264 AppLaunch.exe 30
Processes
-
C:\Users\Admin\AppData\Local\Temp\9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe"C:\Users\Admin\AppData\Local\Temp\9371f17eecb504172e85f4cfb6656b0b406276db4321ce59d05f3442e1505b7e.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2448 -
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:1264 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1264 -s 1963⤵
- Program crash
PID:2672
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2448 -s 922⤵
- Program crash
PID:2432
-