Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
119s -
max time network
137s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
12/10/2023, 16:16
Static task
static1
Behavioral task
behavioral1
Sample
2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe
Resource
win7-20230831-en
Behavioral task
behavioral2
Sample
2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe
Resource
win10v2004-20230915-en
General
-
Target
2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe
-
Size
1.4MB
-
MD5
1179f60ef3ca68ce7dc51abaa7a4f956
-
SHA1
8200951d968115f80d22732100c614b052b98498
-
SHA256
2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85
-
SHA512
8e942078acf3e70e34cfc9e90acf9f9a68c9698e5acac5305e30767f78566607ba2206064414664be1755da15506574bd69cee9568dadba37633189709bdab2c
-
SSDEEP
24576:509CCRqXbsn6oFiKwvIRbs0p38BBipHuuv7F3UQoXJ937O2mKQ:509CCUrAewRI9SuKFEQW93ZQ
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1396 set thread context of 2584 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 30 -
Program crash 1 IoCs
pid pid_target Process procid_target 2764 2584 WerFault.exe 30 -
Suspicious use of WriteProcessMemory 28 IoCs
description pid Process procid_target PID 1396 wrote to memory of 1704 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 28 PID 1396 wrote to memory of 1704 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 28 PID 1396 wrote to memory of 1704 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 28 PID 1396 wrote to memory of 1704 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 28 PID 1396 wrote to memory of 1704 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 28 PID 1396 wrote to memory of 1704 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 28 PID 1396 wrote to memory of 1704 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 28 PID 1396 wrote to memory of 2584 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 30 PID 1396 wrote to memory of 2584 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 30 PID 1396 wrote to memory of 2584 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 30 PID 1396 wrote to memory of 2584 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 30 PID 1396 wrote to memory of 2584 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 30 PID 1396 wrote to memory of 2584 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 30 PID 1396 wrote to memory of 2584 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 30 PID 1396 wrote to memory of 2584 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 30 PID 1396 wrote to memory of 2584 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 30 PID 1396 wrote to memory of 2584 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 30 PID 1396 wrote to memory of 2584 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 30 PID 1396 wrote to memory of 2584 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 30 PID 1396 wrote to memory of 2584 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 30 PID 1396 wrote to memory of 2584 1396 2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe 30 PID 2584 wrote to memory of 2764 2584 AppLaunch.exe 31 PID 2584 wrote to memory of 2764 2584 AppLaunch.exe 31 PID 2584 wrote to memory of 2764 2584 AppLaunch.exe 31 PID 2584 wrote to memory of 2764 2584 AppLaunch.exe 31 PID 2584 wrote to memory of 2764 2584 AppLaunch.exe 31 PID 2584 wrote to memory of 2764 2584 AppLaunch.exe 31 PID 2584 wrote to memory of 2764 2584 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe"C:\Users\Admin\AppData\Local\Temp\2c4bee4a367d7d47452a5e1231d14b97723f37f1ab6741638c6d7c45dfd0fc85.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1396 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1704
-
-
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:2584 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2584 -s 2003⤵
- Program crash
PID:2764
-
-