Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
122s -
max time network
126s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
01/10/2023, 22:18
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe
Resource
win7-20230831-en
3 signatures
300 seconds
General
-
Target
26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe
-
Size
356KB
-
MD5
0e1af181ab372bea675f0b6a42e89cc1
-
SHA1
50ab08a8c9234bb0a4b631e8e37ca6760e8ec8c3
-
SHA256
26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230
-
SHA512
c4f3e90cb53e40ae91472d9e30120a8093728e850a907a237da98c5be9daf56c6f2d0e0f21d452981b0ee5fd8a06ddca4f06758d67f3c70c47c3157546f8df87
-
SSDEEP
6144:HlTeW/s5GqrO5aXnfEGIXWPvZAOwy23kOMms5yEd4h2mLXjuNVs0BC+:kmcGqrOk86xMls5NOjjKs0BC+
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2864 set thread context of 2132 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 29 -
Program crash 2 IoCs
pid pid_target Process procid_target 2772 2864 WerFault.exe 15 2792 2132 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 2864 wrote to memory of 2132 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 29 PID 2864 wrote to memory of 2132 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 29 PID 2864 wrote to memory of 2132 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 29 PID 2864 wrote to memory of 2132 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 29 PID 2864 wrote to memory of 2132 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 29 PID 2864 wrote to memory of 2132 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 29 PID 2864 wrote to memory of 2132 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 29 PID 2864 wrote to memory of 2132 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 29 PID 2864 wrote to memory of 2132 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 29 PID 2864 wrote to memory of 2132 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 29 PID 2864 wrote to memory of 2132 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 29 PID 2864 wrote to memory of 2132 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 29 PID 2864 wrote to memory of 2132 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 29 PID 2864 wrote to memory of 2132 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 29 PID 2864 wrote to memory of 2772 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 30 PID 2864 wrote to memory of 2772 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 30 PID 2864 wrote to memory of 2772 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 30 PID 2864 wrote to memory of 2772 2864 26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe 30 PID 2132 wrote to memory of 2792 2132 AppLaunch.exe 31 PID 2132 wrote to memory of 2792 2132 AppLaunch.exe 31 PID 2132 wrote to memory of 2792 2132 AppLaunch.exe 31 PID 2132 wrote to memory of 2792 2132 AppLaunch.exe 31 PID 2132 wrote to memory of 2792 2132 AppLaunch.exe 31 PID 2132 wrote to memory of 2792 2132 AppLaunch.exe 31 PID 2132 wrote to memory of 2792 2132 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe"C:\Users\Admin\AppData\Local\Temp\26ee612a810e2f60b4ff3008d537e8a9e31b3934b855ec563f905646f30d9230.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2864 -
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:2132 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2132 -s 1963⤵
- Program crash
PID:2792
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2864 -s 762⤵
- Program crash
PID:2772
-