Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
119s -
max time network
123s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
12/10/2023, 16:43
Static task
static1
Behavioral task
behavioral1
Sample
835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe
-
Size
371KB
-
MD5
551ecb88185fb0a79f81f0e126a27dd4
-
SHA1
7791b6f5c3907e61a7f87c3977d7738fd15b8459
-
SHA256
835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504
-
SHA512
a05d647f1fea2714efca3c087d7eb91844149df895c52f6cdc0c624ec48b22f22dcf46da4f2e264152ac4d58d3a6d946316a4c65893652b26419834465e86dba
-
SSDEEP
6144:0OvJm09zORs+z/TMify9DAOQgQi7mJ2L8Kh6L0wbZkcjJB3+O8/:02w09CK5NPT7UA2pvV8/
Malware Config
Signatures
-
Detect Mystic stealer payload 6 IoCs
resource yara_rule behavioral1/memory/2596-3-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2596-4-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2596-5-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2596-7-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2596-9-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic behavioral1/memory/2596-11-0x0000000000400000-0x0000000000428000-memory.dmp family_mystic -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2456 set thread context of 2596 2456 835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe 28 -
Program crash 1 IoCs
pid pid_target Process procid_target 1728 2596 WerFault.exe 28 -
Suspicious use of WriteProcessMemory 21 IoCs
description pid Process procid_target PID 2456 wrote to memory of 2596 2456 835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe 28 PID 2456 wrote to memory of 2596 2456 835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe 28 PID 2456 wrote to memory of 2596 2456 835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe 28 PID 2456 wrote to memory of 2596 2456 835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe 28 PID 2456 wrote to memory of 2596 2456 835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe 28 PID 2456 wrote to memory of 2596 2456 835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe 28 PID 2456 wrote to memory of 2596 2456 835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe 28 PID 2456 wrote to memory of 2596 2456 835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe 28 PID 2456 wrote to memory of 2596 2456 835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe 28 PID 2456 wrote to memory of 2596 2456 835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe 28 PID 2456 wrote to memory of 2596 2456 835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe 28 PID 2456 wrote to memory of 2596 2456 835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe 28 PID 2456 wrote to memory of 2596 2456 835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe 28 PID 2456 wrote to memory of 2596 2456 835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe 28 PID 2596 wrote to memory of 1728 2596 AppLaunch.exe 29 PID 2596 wrote to memory of 1728 2596 AppLaunch.exe 29 PID 2596 wrote to memory of 1728 2596 AppLaunch.exe 29 PID 2596 wrote to memory of 1728 2596 AppLaunch.exe 29 PID 2596 wrote to memory of 1728 2596 AppLaunch.exe 29 PID 2596 wrote to memory of 1728 2596 AppLaunch.exe 29 PID 2596 wrote to memory of 1728 2596 AppLaunch.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe"C:\Users\Admin\AppData\Local\Temp\835704f5f60f193feb9ca8cdd6d968243ebc2fa2c263f8281e4dd45b27b22504.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2456 -
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:2596 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2596 -s 1963⤵
- Program crash
PID:1728
-
-