Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
105s -
max time network
150s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
11/10/2023, 22:57
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
a21205f09e29e9b915b65d28633d88e892e7c9df4bcaba65bc07c770d74320a0.exe
Resource
win7-20230831-en
3 signatures
150 seconds
General
-
Target
a21205f09e29e9b915b65d28633d88e892e7c9df4bcaba65bc07c770d74320a0.exe
-
Size
364KB
-
MD5
de4f1f53ada869dd31f37d881ed70f6f
-
SHA1
483f09ac2dbc351010985205dfe8e10b371caa74
-
SHA256
a21205f09e29e9b915b65d28633d88e892e7c9df4bcaba65bc07c770d74320a0
-
SHA512
375db472a9a8afee8823375751ac4af850a2ef9921463519f7bf0961145220ff90e774de6876dbb61627b0cf6603bd8c7bb99808eb69e0de62fe132cbb3a5164
-
SSDEEP
6144:3646fuYXChoQTjlFgLuCY1dRuAOfallWNTzjD4LoBFqql8gDP4w8y0:3/YzXChdTbv1buUQNjELoD8gkw8y
Malware Config
Extracted
Family
mystic
C2
http://5.42.92.211/loghub/master
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2076 set thread context of 5108 2076 a21205f09e29e9b915b65d28633d88e892e7c9df4bcaba65bc07c770d74320a0.exe 87 -
Program crash 1 IoCs
pid pid_target Process procid_target 4964 2076 WerFault.exe 83 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 2076 wrote to memory of 5108 2076 a21205f09e29e9b915b65d28633d88e892e7c9df4bcaba65bc07c770d74320a0.exe 87 PID 2076 wrote to memory of 5108 2076 a21205f09e29e9b915b65d28633d88e892e7c9df4bcaba65bc07c770d74320a0.exe 87 PID 2076 wrote to memory of 5108 2076 a21205f09e29e9b915b65d28633d88e892e7c9df4bcaba65bc07c770d74320a0.exe 87 PID 2076 wrote to memory of 5108 2076 a21205f09e29e9b915b65d28633d88e892e7c9df4bcaba65bc07c770d74320a0.exe 87 PID 2076 wrote to memory of 5108 2076 a21205f09e29e9b915b65d28633d88e892e7c9df4bcaba65bc07c770d74320a0.exe 87 PID 2076 wrote to memory of 5108 2076 a21205f09e29e9b915b65d28633d88e892e7c9df4bcaba65bc07c770d74320a0.exe 87 PID 2076 wrote to memory of 5108 2076 a21205f09e29e9b915b65d28633d88e892e7c9df4bcaba65bc07c770d74320a0.exe 87 PID 2076 wrote to memory of 5108 2076 a21205f09e29e9b915b65d28633d88e892e7c9df4bcaba65bc07c770d74320a0.exe 87 PID 2076 wrote to memory of 5108 2076 a21205f09e29e9b915b65d28633d88e892e7c9df4bcaba65bc07c770d74320a0.exe 87 PID 2076 wrote to memory of 5108 2076 a21205f09e29e9b915b65d28633d88e892e7c9df4bcaba65bc07c770d74320a0.exe 87
Processes
-
C:\Users\Admin\AppData\Local\Temp\a21205f09e29e9b915b65d28633d88e892e7c9df4bcaba65bc07c770d74320a0.exe"C:\Users\Admin\AppData\Local\Temp\a21205f09e29e9b915b65d28633d88e892e7c9df4bcaba65bc07c770d74320a0.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2076 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:5108
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2076 -s 2362⤵
- Program crash
PID:4964
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 468 -p 2076 -ip 20761⤵PID:1164