Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
118s -
max time network
143s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
11/10/2023, 20:46
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe
Resource
win7-20230831-en
3 signatures
150 seconds
General
-
Target
1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe
-
Size
364KB
-
MD5
a77a497f68f991f18240a4968f3b8521
-
SHA1
9bf8b5803f7224a3d66d904d205c18ac64aa7cf6
-
SHA256
1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191
-
SHA512
50e4f3d68b48e975fcc0d63997cea85b3287a279becc35bf4244744f5f9ec51bed9c85f8b7a6b23a51dbeca41969558e87d3d8bd2954568d82cfb5ee0a232cd6
-
SSDEEP
6144:iy46fuYXChoQTjlFgLuCY1dRuAOCHuH2yiZwyZwZxhXmXXXXXXXR59yw8y0:iXYzXChdTbv1buNiZwDZ7XOnnnRnyw8y
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2604 set thread context of 2424 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 29 -
Program crash 2 IoCs
pid pid_target Process procid_target 2228 2604 WerFault.exe 17 2800 2424 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 32 IoCs
description pid Process procid_target PID 2604 wrote to memory of 2456 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 28 PID 2604 wrote to memory of 2456 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 28 PID 2604 wrote to memory of 2456 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 28 PID 2604 wrote to memory of 2456 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 28 PID 2604 wrote to memory of 2456 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 28 PID 2604 wrote to memory of 2456 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 28 PID 2604 wrote to memory of 2456 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 28 PID 2604 wrote to memory of 2424 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 29 PID 2604 wrote to memory of 2424 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 29 PID 2604 wrote to memory of 2424 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 29 PID 2604 wrote to memory of 2424 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 29 PID 2604 wrote to memory of 2424 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 29 PID 2604 wrote to memory of 2424 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 29 PID 2604 wrote to memory of 2424 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 29 PID 2604 wrote to memory of 2424 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 29 PID 2604 wrote to memory of 2424 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 29 PID 2604 wrote to memory of 2424 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 29 PID 2604 wrote to memory of 2424 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 29 PID 2604 wrote to memory of 2424 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 29 PID 2604 wrote to memory of 2424 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 29 PID 2604 wrote to memory of 2424 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 29 PID 2604 wrote to memory of 2228 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 30 PID 2604 wrote to memory of 2228 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 30 PID 2604 wrote to memory of 2228 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 30 PID 2604 wrote to memory of 2228 2604 1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe 30 PID 2424 wrote to memory of 2800 2424 AppLaunch.exe 31 PID 2424 wrote to memory of 2800 2424 AppLaunch.exe 31 PID 2424 wrote to memory of 2800 2424 AppLaunch.exe 31 PID 2424 wrote to memory of 2800 2424 AppLaunch.exe 31 PID 2424 wrote to memory of 2800 2424 AppLaunch.exe 31 PID 2424 wrote to memory of 2800 2424 AppLaunch.exe 31 PID 2424 wrote to memory of 2800 2424 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe"C:\Users\Admin\AppData\Local\Temp\1319d7501351f1023273cda386fbde4dea62cb7de9b3a2a5b38f5e7f51407191.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2604 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2456
-
-
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:2424 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2424 -s 1963⤵
- Program crash
PID:2800
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2604 -s 602⤵
- Program crash
PID:2228
-