Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
172s -
max time network
181s -
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, 21:54
Static task
static1
Behavioral task
behavioral1
Sample
43c9d5192e280fb9c969d3a50b015b0f573e092ff9d78c4f96bf324124eac468.exe
Resource
win7-20230831-en
3 signatures
150 seconds
General
-
Target
43c9d5192e280fb9c969d3a50b015b0f573e092ff9d78c4f96bf324124eac468.exe
-
Size
396KB
-
MD5
d264869406b4cb09110b6b8af5456b37
-
SHA1
bdbbd0bc70c9c2dd1b667e475fcf61479c3ce2aa
-
SHA256
43c9d5192e280fb9c969d3a50b015b0f573e092ff9d78c4f96bf324124eac468
-
SHA512
b3f8b707774f15acae65e4a8bf0c85fdc18a64a0e17226de845383aa6bce41a49b85e20539ba5e0351621ccd374eb07d4f7c990c43d707a7865f4114de9ea597
-
SSDEEP
12288:TNcdqW5sEe2uusc5vWDGS1/Q6oCmNtIDU7mhol8Mwh:TNct5vv5XS1/Q0mNtIDU7mholWh
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 4964 set thread context of 2008 4964 43c9d5192e280fb9c969d3a50b015b0f573e092ff9d78c4f96bf324124eac468.exe 87 -
Program crash 1 IoCs
pid pid_target Process procid_target 2140 4964 WerFault.exe 83 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4964 wrote to memory of 2008 4964 43c9d5192e280fb9c969d3a50b015b0f573e092ff9d78c4f96bf324124eac468.exe 87 PID 4964 wrote to memory of 2008 4964 43c9d5192e280fb9c969d3a50b015b0f573e092ff9d78c4f96bf324124eac468.exe 87 PID 4964 wrote to memory of 2008 4964 43c9d5192e280fb9c969d3a50b015b0f573e092ff9d78c4f96bf324124eac468.exe 87 PID 4964 wrote to memory of 2008 4964 43c9d5192e280fb9c969d3a50b015b0f573e092ff9d78c4f96bf324124eac468.exe 87 PID 4964 wrote to memory of 2008 4964 43c9d5192e280fb9c969d3a50b015b0f573e092ff9d78c4f96bf324124eac468.exe 87 PID 4964 wrote to memory of 2008 4964 43c9d5192e280fb9c969d3a50b015b0f573e092ff9d78c4f96bf324124eac468.exe 87 PID 4964 wrote to memory of 2008 4964 43c9d5192e280fb9c969d3a50b015b0f573e092ff9d78c4f96bf324124eac468.exe 87 PID 4964 wrote to memory of 2008 4964 43c9d5192e280fb9c969d3a50b015b0f573e092ff9d78c4f96bf324124eac468.exe 87 PID 4964 wrote to memory of 2008 4964 43c9d5192e280fb9c969d3a50b015b0f573e092ff9d78c4f96bf324124eac468.exe 87 PID 4964 wrote to memory of 2008 4964 43c9d5192e280fb9c969d3a50b015b0f573e092ff9d78c4f96bf324124eac468.exe 87
Processes
-
C:\Users\Admin\AppData\Local\Temp\43c9d5192e280fb9c969d3a50b015b0f573e092ff9d78c4f96bf324124eac468.exe"C:\Users\Admin\AppData\Local\Temp\43c9d5192e280fb9c969d3a50b015b0f573e092ff9d78c4f96bf324124eac468.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4964 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2008
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4964 -s 2522⤵
- Program crash
PID:2140
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 432 -p 4964 -ip 49641⤵PID:4716