Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
120s -
max time network
126s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
12/10/2023, 22:18 UTC
Static task
static1
Behavioral task
behavioral1
Sample
3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe
Resource
win7-20230831-en
Behavioral task
behavioral2
Sample
3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe
Resource
win10v2004-20230915-en
General
-
Target
3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe
-
Size
1.2MB
-
MD5
20495df89962673387ca7b9925e4f434
-
SHA1
73970d9530574f3bd2912ab6dc797391c60d9cfc
-
SHA256
3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302
-
SHA512
cdef891691bf2d6ced9c74d662ce7f058548149f7ece07574a52b99421b98da40cd407fcacc9651acace8f4a31fd661bdc5b49e897478e36e27ccfd8b4a8d8e5
-
SSDEEP
24576:wZtQ76aJrc/lYW3RxIZ+MxbcGAVa0Ga7okOMhZ:wZtQeaJrZZ+MxbD+s4MMhZ
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3040 set thread context of 2624 3040 3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe 29 -
Program crash 1 IoCs
pid pid_target Process procid_target 2640 2624 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 21 IoCs
description pid Process procid_target PID 3040 wrote to memory of 2624 3040 3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe 29 PID 3040 wrote to memory of 2624 3040 3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe 29 PID 3040 wrote to memory of 2624 3040 3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe 29 PID 3040 wrote to memory of 2624 3040 3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe 29 PID 3040 wrote to memory of 2624 3040 3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe 29 PID 3040 wrote to memory of 2624 3040 3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe 29 PID 3040 wrote to memory of 2624 3040 3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe 29 PID 3040 wrote to memory of 2624 3040 3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe 29 PID 3040 wrote to memory of 2624 3040 3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe 29 PID 3040 wrote to memory of 2624 3040 3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe 29 PID 3040 wrote to memory of 2624 3040 3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe 29 PID 3040 wrote to memory of 2624 3040 3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe 29 PID 3040 wrote to memory of 2624 3040 3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe 29 PID 3040 wrote to memory of 2624 3040 3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe 29 PID 2624 wrote to memory of 2640 2624 AppLaunch.exe 30 PID 2624 wrote to memory of 2640 2624 AppLaunch.exe 30 PID 2624 wrote to memory of 2640 2624 AppLaunch.exe 30 PID 2624 wrote to memory of 2640 2624 AppLaunch.exe 30 PID 2624 wrote to memory of 2640 2624 AppLaunch.exe 30 PID 2624 wrote to memory of 2640 2624 AppLaunch.exe 30 PID 2624 wrote to memory of 2640 2624 AppLaunch.exe 30
Processes
-
C:\Users\Admin\AppData\Local\Temp\3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe"C:\Users\Admin\AppData\Local\Temp\3d4ad0f7c5b92d3dadbc2e789a414b4a074ef92a4fea40ae825e1a3123c24302_JC.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3040 -
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:2624 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2624 -s 2003⤵
- Program crash
PID:2640
-
-