Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
122s -
max time network
154s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
11/10/2023, 21:49
Static task
static1
Behavioral task
behavioral1
Sample
34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe
Resource
win7-20230831-en
3 signatures
150 seconds
General
-
Target
34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe
-
Size
396KB
-
MD5
cad9825c418c43689417ecb32cd258f1
-
SHA1
85a1c7fe4e6f7b180888314d4a7dc5f9c1ce5b80
-
SHA256
34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83
-
SHA512
a573945e422f269477ba401c17ec5a5a5ad2a92174e0109e03bd351fc3fa4e5ed01873c34a50b4565b655b2747bf7a0cf41402230afc70461b2d43b7e0c0379b
-
SSDEEP
6144:uNMKhUOqW5XJ6EDOpvOCm5MNuAODA9ajTp1w6lfK9VYNbQTeqwh:uN1dqW5sEe2uuNA9ajd1w6lK9+Nb+wh
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2244 set thread context of 2440 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 29 -
Program crash 2 IoCs
pid pid_target Process procid_target 1736 2244 WerFault.exe 7 2160 2440 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 32 IoCs
description pid Process procid_target PID 2244 wrote to memory of 2200 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 28 PID 2244 wrote to memory of 2200 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 28 PID 2244 wrote to memory of 2200 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 28 PID 2244 wrote to memory of 2200 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 28 PID 2244 wrote to memory of 2200 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 28 PID 2244 wrote to memory of 2200 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 28 PID 2244 wrote to memory of 2200 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 28 PID 2244 wrote to memory of 2440 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 29 PID 2244 wrote to memory of 2440 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 29 PID 2244 wrote to memory of 2440 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 29 PID 2244 wrote to memory of 2440 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 29 PID 2244 wrote to memory of 2440 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 29 PID 2244 wrote to memory of 2440 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 29 PID 2244 wrote to memory of 2440 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 29 PID 2244 wrote to memory of 2440 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 29 PID 2244 wrote to memory of 2440 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 29 PID 2244 wrote to memory of 2440 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 29 PID 2244 wrote to memory of 2440 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 29 PID 2244 wrote to memory of 2440 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 29 PID 2244 wrote to memory of 2440 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 29 PID 2244 wrote to memory of 2440 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 29 PID 2244 wrote to memory of 1736 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 30 PID 2244 wrote to memory of 1736 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 30 PID 2244 wrote to memory of 1736 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 30 PID 2244 wrote to memory of 1736 2244 34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe 30 PID 2440 wrote to memory of 2160 2440 AppLaunch.exe 31 PID 2440 wrote to memory of 2160 2440 AppLaunch.exe 31 PID 2440 wrote to memory of 2160 2440 AppLaunch.exe 31 PID 2440 wrote to memory of 2160 2440 AppLaunch.exe 31 PID 2440 wrote to memory of 2160 2440 AppLaunch.exe 31 PID 2440 wrote to memory of 2160 2440 AppLaunch.exe 31 PID 2440 wrote to memory of 2160 2440 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe"C:\Users\Admin\AppData\Local\Temp\34a337ff53f7c7c7d35351ba65e7a0a52d60aab36398fbd17ee6d3ca1bbbeb83.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2244 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2200
-
-
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:2440 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2440 -s 1963⤵
- Program crash
PID:2160
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2244 -s 602⤵
- Program crash
PID:1736
-