Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
125s -
max time network
134s -
platform
windows10-1703_x64 -
resource
win10-20230915-en -
resource tags
arch:x64arch:x86image:win10-20230915-enlocale:en-usos:windows10-1703-x64system -
submitted
08/10/2023, 11:27
Static task
static1
Behavioral task
behavioral1
Sample
c75131770e0642d4379faf917d254647b2b4cfb94a1a5d7971337d1ea979513d.exe
Resource
win10-20230915-en
3 signatures
150 seconds
General
-
Target
c75131770e0642d4379faf917d254647b2b4cfb94a1a5d7971337d1ea979513d.exe
-
Size
423KB
-
MD5
4fd482e292ab85b8d8dd4babd7fd2777
-
SHA1
b0be96e94e1c84fc0970cc5ceb3ac05d636ef3a3
-
SHA256
c75131770e0642d4379faf917d254647b2b4cfb94a1a5d7971337d1ea979513d
-
SHA512
1380090b4287e90b86d0e85c9089923f7a281c26c0e9ed6fe27549fddfba362e378f5db38b8205a1cf4dbd7ef16a246cc9c1db7ab9853b7bf27f3605b2a3aeb2
-
SSDEEP
6144:DE/2uY/1SBRHwc13NR8Ca/XU6JAOMXhWZop5rFcUDw6Dwx/U17mPOIrMsA1S:Djr/1SBZlW/1JuXhX5BcUDw6Y/oLsA1S
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 32 set thread context of 296 32 c75131770e0642d4379faf917d254647b2b4cfb94a1a5d7971337d1ea979513d.exe 70 -
Program crash 1 IoCs
pid pid_target Process procid_target 4472 32 WerFault.exe 69 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 32 wrote to memory of 296 32 c75131770e0642d4379faf917d254647b2b4cfb94a1a5d7971337d1ea979513d.exe 70 PID 32 wrote to memory of 296 32 c75131770e0642d4379faf917d254647b2b4cfb94a1a5d7971337d1ea979513d.exe 70 PID 32 wrote to memory of 296 32 c75131770e0642d4379faf917d254647b2b4cfb94a1a5d7971337d1ea979513d.exe 70 PID 32 wrote to memory of 296 32 c75131770e0642d4379faf917d254647b2b4cfb94a1a5d7971337d1ea979513d.exe 70 PID 32 wrote to memory of 296 32 c75131770e0642d4379faf917d254647b2b4cfb94a1a5d7971337d1ea979513d.exe 70 PID 32 wrote to memory of 296 32 c75131770e0642d4379faf917d254647b2b4cfb94a1a5d7971337d1ea979513d.exe 70 PID 32 wrote to memory of 296 32 c75131770e0642d4379faf917d254647b2b4cfb94a1a5d7971337d1ea979513d.exe 70 PID 32 wrote to memory of 296 32 c75131770e0642d4379faf917d254647b2b4cfb94a1a5d7971337d1ea979513d.exe 70 PID 32 wrote to memory of 296 32 c75131770e0642d4379faf917d254647b2b4cfb94a1a5d7971337d1ea979513d.exe 70 PID 32 wrote to memory of 296 32 c75131770e0642d4379faf917d254647b2b4cfb94a1a5d7971337d1ea979513d.exe 70
Processes
-
C:\Users\Admin\AppData\Local\Temp\c75131770e0642d4379faf917d254647b2b4cfb94a1a5d7971337d1ea979513d.exe"C:\Users\Admin\AppData\Local\Temp\c75131770e0642d4379faf917d254647b2b4cfb94a1a5d7971337d1ea979513d.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:32 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:296
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 32 -s 3202⤵
- Program crash
PID:4472
-