Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
120s -
max time network
144s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
12/10/2023, 12:57
Static task
static1
Behavioral task
behavioral1
Sample
b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe
Resource
win7-20230831-en
Behavioral task
behavioral2
Sample
b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe
Resource
win10v2004-20230915-en
General
-
Target
b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe
-
Size
1.4MB
-
MD5
fa074735dd47f60a825d97a08d98a33d
-
SHA1
cbeca43ef31e64047ae1d22eb51390df0a413a79
-
SHA256
b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377
-
SHA512
750aed8497fd007128285e42f3bde764799e4dd6218f07fd681807091d9a944afae9645c630b1178a65362b323e5d7600a54761eeaf6b73ba2d5ca28e9772486
-
SSDEEP
24576:gJYSgG+lqO7/38XOKQi7skivRePwCY1hQ+HIIqCA4UrXQM1q8dYf:ZSgG+0M/38tUsD7+o5r1Sf
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2068 set thread context of 2748 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 31 -
Program crash 2 IoCs
pid pid_target Process procid_target 2520 2068 WerFault.exe 15 2660 2748 WerFault.exe 31 -
Suspicious use of WriteProcessMemory 32 IoCs
description pid Process procid_target PID 2068 wrote to memory of 2824 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 30 PID 2068 wrote to memory of 2824 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 30 PID 2068 wrote to memory of 2824 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 30 PID 2068 wrote to memory of 2824 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 30 PID 2068 wrote to memory of 2824 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 30 PID 2068 wrote to memory of 2824 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 30 PID 2068 wrote to memory of 2824 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 30 PID 2068 wrote to memory of 2748 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 31 PID 2068 wrote to memory of 2748 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 31 PID 2068 wrote to memory of 2748 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 31 PID 2068 wrote to memory of 2748 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 31 PID 2068 wrote to memory of 2748 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 31 PID 2068 wrote to memory of 2748 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 31 PID 2068 wrote to memory of 2748 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 31 PID 2068 wrote to memory of 2748 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 31 PID 2068 wrote to memory of 2748 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 31 PID 2068 wrote to memory of 2748 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 31 PID 2068 wrote to memory of 2748 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 31 PID 2068 wrote to memory of 2748 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 31 PID 2068 wrote to memory of 2748 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 31 PID 2068 wrote to memory of 2748 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 31 PID 2068 wrote to memory of 2520 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 32 PID 2068 wrote to memory of 2520 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 32 PID 2068 wrote to memory of 2520 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 32 PID 2068 wrote to memory of 2520 2068 b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe 32 PID 2748 wrote to memory of 2660 2748 AppLaunch.exe 33 PID 2748 wrote to memory of 2660 2748 AppLaunch.exe 33 PID 2748 wrote to memory of 2660 2748 AppLaunch.exe 33 PID 2748 wrote to memory of 2660 2748 AppLaunch.exe 33 PID 2748 wrote to memory of 2660 2748 AppLaunch.exe 33 PID 2748 wrote to memory of 2660 2748 AppLaunch.exe 33 PID 2748 wrote to memory of 2660 2748 AppLaunch.exe 33
Processes
-
C:\Users\Admin\AppData\Local\Temp\b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe"C:\Users\Admin\AppData\Local\Temp\b97cf8e14076f75497c53ea069997c4cd6275387907c210a5b45059c2c49c377.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2068 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2824
-
-
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:2748 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2748 -s 2003⤵
- Program crash
PID:2660
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2068 -s 1002⤵
- Program crash
PID:2520
-