Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
15s -
max time network
18s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
21/09/2023, 07:16
Static task
static1
Behavioral task
behavioral1
Sample
6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe
Resource
win7-20230831-en
3 signatures
30 seconds
General
-
Target
6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe
-
Size
1.1MB
-
MD5
f12fc309c458758c9d194ed3c8c586d7
-
SHA1
11ccf902dc324dfda56d958fde787f88057c3195
-
SHA256
6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58
-
SHA512
9dcb225fd64b457c75d093f753d015ab0e43a4c1cdda80b3ef55f8927bb95f7d7afb20b339b9fb127e7250a308b006aef73590c7f854d0f6535165e8db3e5dfa
-
SSDEEP
12288:ENsowN2dA1IY9i4ytPDxZZZVf95Tjz8L2aB4vIubLkk8rkJa2EADdLCAW:6so62dA1h9i4ytXVX3dTaXAW
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1712 set thread context of 3060 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 30 -
Program crash 2 IoCs
pid pid_target Process procid_target 2696 1712 WerFault.exe 24 2916 3060 WerFault.exe 30 -
Suspicious use of WriteProcessMemory 32 IoCs
description pid Process procid_target PID 1712 wrote to memory of 2996 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 29 PID 1712 wrote to memory of 2996 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 29 PID 1712 wrote to memory of 2996 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 29 PID 1712 wrote to memory of 2996 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 29 PID 1712 wrote to memory of 2996 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 29 PID 1712 wrote to memory of 2996 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 29 PID 1712 wrote to memory of 2996 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 29 PID 1712 wrote to memory of 3060 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 30 PID 1712 wrote to memory of 3060 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 30 PID 1712 wrote to memory of 3060 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 30 PID 1712 wrote to memory of 3060 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 30 PID 1712 wrote to memory of 3060 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 30 PID 1712 wrote to memory of 3060 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 30 PID 1712 wrote to memory of 3060 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 30 PID 1712 wrote to memory of 3060 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 30 PID 1712 wrote to memory of 3060 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 30 PID 1712 wrote to memory of 3060 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 30 PID 1712 wrote to memory of 3060 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 30 PID 1712 wrote to memory of 3060 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 30 PID 1712 wrote to memory of 3060 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 30 PID 1712 wrote to memory of 3060 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 30 PID 1712 wrote to memory of 2696 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 31 PID 1712 wrote to memory of 2696 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 31 PID 1712 wrote to memory of 2696 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 31 PID 1712 wrote to memory of 2696 1712 6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe 31 PID 3060 wrote to memory of 2916 3060 AppLaunch.exe 32 PID 3060 wrote to memory of 2916 3060 AppLaunch.exe 32 PID 3060 wrote to memory of 2916 3060 AppLaunch.exe 32 PID 3060 wrote to memory of 2916 3060 AppLaunch.exe 32 PID 3060 wrote to memory of 2916 3060 AppLaunch.exe 32 PID 3060 wrote to memory of 2916 3060 AppLaunch.exe 32 PID 3060 wrote to memory of 2916 3060 AppLaunch.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe"C:\Users\Admin\AppData\Local\Temp\6f8e9477d54e48402791f83e2b6db395c3e6566ea83ad6af77f50b62025e1e58.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1712 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2996
-
-
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:3060 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3060 -s 1963⤵
- Program crash
PID:2916
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1712 -s 1002⤵
- Program crash
PID:2696
-