Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
146s -
max time network
153s -
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, 16:46
Static task
static1
Behavioral task
behavioral1
Sample
b82895964dcd2bc25bd94d15882e352369d4a2e326dabccce89571f7a9c76cd6.exe
Resource
win7-20230831-en
3 signatures
150 seconds
General
-
Target
b82895964dcd2bc25bd94d15882e352369d4a2e326dabccce89571f7a9c76cd6.exe
-
Size
372KB
-
MD5
2d5d8d55e461986b5f3245d0a73a6643
-
SHA1
755070b71b3fa2a8446256d0c0dac54be95b63fb
-
SHA256
b82895964dcd2bc25bd94d15882e352369d4a2e326dabccce89571f7a9c76cd6
-
SHA512
6f2948c711f63409ade4ced1512618c91e8a92972de39861642cb72aac19e944ac2adb7a0f46ab8a9e663da0702a8e70747eb5e3ded8b51b344a8e73cefafce0
-
SSDEEP
6144:Pq46fuYXChoQTjlFgLuCY1dRuAO3xkqJkcEsu1OGxkE7VRw8y0M:PPYzXChdTbv1buUqJMsXGyEVRw8yr
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 2680 set thread context of 2644 2680 b82895964dcd2bc25bd94d15882e352369d4a2e326dabccce89571f7a9c76cd6.exe 86 -
Program crash 1 IoCs
pid pid_target Process procid_target 4920 2680 WerFault.exe 83 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 2680 wrote to memory of 2644 2680 b82895964dcd2bc25bd94d15882e352369d4a2e326dabccce89571f7a9c76cd6.exe 86 PID 2680 wrote to memory of 2644 2680 b82895964dcd2bc25bd94d15882e352369d4a2e326dabccce89571f7a9c76cd6.exe 86 PID 2680 wrote to memory of 2644 2680 b82895964dcd2bc25bd94d15882e352369d4a2e326dabccce89571f7a9c76cd6.exe 86 PID 2680 wrote to memory of 2644 2680 b82895964dcd2bc25bd94d15882e352369d4a2e326dabccce89571f7a9c76cd6.exe 86 PID 2680 wrote to memory of 2644 2680 b82895964dcd2bc25bd94d15882e352369d4a2e326dabccce89571f7a9c76cd6.exe 86 PID 2680 wrote to memory of 2644 2680 b82895964dcd2bc25bd94d15882e352369d4a2e326dabccce89571f7a9c76cd6.exe 86 PID 2680 wrote to memory of 2644 2680 b82895964dcd2bc25bd94d15882e352369d4a2e326dabccce89571f7a9c76cd6.exe 86 PID 2680 wrote to memory of 2644 2680 b82895964dcd2bc25bd94d15882e352369d4a2e326dabccce89571f7a9c76cd6.exe 86 PID 2680 wrote to memory of 2644 2680 b82895964dcd2bc25bd94d15882e352369d4a2e326dabccce89571f7a9c76cd6.exe 86 PID 2680 wrote to memory of 2644 2680 b82895964dcd2bc25bd94d15882e352369d4a2e326dabccce89571f7a9c76cd6.exe 86
Processes
-
C:\Users\Admin\AppData\Local\Temp\b82895964dcd2bc25bd94d15882e352369d4a2e326dabccce89571f7a9c76cd6.exe"C:\Users\Admin\AppData\Local\Temp\b82895964dcd2bc25bd94d15882e352369d4a2e326dabccce89571f7a9c76cd6.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2680 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2644
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2680 -s 2402⤵
- Program crash
PID:4920
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 444 -p 2680 -ip 26801⤵PID:396