Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
145s -
max time network
148s -
platform
windows10-2004_x64 -
resource
win10v2004-20231215-en -
resource tags
arch:x64arch:x86image:win10v2004-20231215-enlocale:en-usos:windows10-2004-x64system -
submitted
30/12/2023, 02:14
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
0b508e8a07b91758e0240bb5a881a0bb.exe
Resource
win7-20231129-en
3 signatures
150 seconds
Behavioral task
behavioral2
Sample
0b508e8a07b91758e0240bb5a881a0bb.exe
Resource
win10v2004-20231215-en
3 signatures
150 seconds
General
-
Target
0b508e8a07b91758e0240bb5a881a0bb.exe
-
Size
84KB
-
MD5
0b508e8a07b91758e0240bb5a881a0bb
-
SHA1
43caaf2bb84394547805903616714e7dede32025
-
SHA256
4499ff51f9e44e4a55b0d2f33d1791ee1f18c60e4b472c274bfadde149c992dc
-
SHA512
9595b823aeddfb36e9c21908c8b890106f30e4c8a336259b353718acf9ad157c8549d8a8d583bcd9fe7084049a0f73183214e6efbc3472d652c7c3478cc42359
-
SSDEEP
1536:uc1tCIbP5Q++oqcLaGv6SzLdeytury3J5MWY3cYsmgSwPMJ0:uc1tCIK++omGv6CLdbtury33/xNdv
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4492 set thread context of 4256 4492 0b508e8a07b91758e0240bb5a881a0bb.exe 21 -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 4256 0b508e8a07b91758e0240bb5a881a0bb.exe 4256 0b508e8a07b91758e0240bb5a881a0bb.exe 4256 0b508e8a07b91758e0240bb5a881a0bb.exe 4256 0b508e8a07b91758e0240bb5a881a0bb.exe -
Suspicious use of WriteProcessMemory 13 IoCs
description pid Process procid_target PID 4492 wrote to memory of 4256 4492 0b508e8a07b91758e0240bb5a881a0bb.exe 21 PID 4492 wrote to memory of 4256 4492 0b508e8a07b91758e0240bb5a881a0bb.exe 21 PID 4492 wrote to memory of 4256 4492 0b508e8a07b91758e0240bb5a881a0bb.exe 21 PID 4492 wrote to memory of 4256 4492 0b508e8a07b91758e0240bb5a881a0bb.exe 21 PID 4492 wrote to memory of 4256 4492 0b508e8a07b91758e0240bb5a881a0bb.exe 21 PID 4492 wrote to memory of 4256 4492 0b508e8a07b91758e0240bb5a881a0bb.exe 21 PID 4492 wrote to memory of 4256 4492 0b508e8a07b91758e0240bb5a881a0bb.exe 21 PID 4256 wrote to memory of 3520 4256 0b508e8a07b91758e0240bb5a881a0bb.exe 52 PID 4256 wrote to memory of 3520 4256 0b508e8a07b91758e0240bb5a881a0bb.exe 52 PID 4256 wrote to memory of 3520 4256 0b508e8a07b91758e0240bb5a881a0bb.exe 52 PID 4256 wrote to memory of 3520 4256 0b508e8a07b91758e0240bb5a881a0bb.exe 52 PID 4256 wrote to memory of 3520 4256 0b508e8a07b91758e0240bb5a881a0bb.exe 52 PID 4256 wrote to memory of 3520 4256 0b508e8a07b91758e0240bb5a881a0bb.exe 52
Processes
-
C:\Users\Admin\AppData\Local\Temp\0b508e8a07b91758e0240bb5a881a0bb.exe"C:\Users\Admin\AppData\Local\Temp\0b508e8a07b91758e0240bb5a881a0bb.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4492 -
C:\Users\Admin\AppData\Local\Temp\0b508e8a07b91758e0240bb5a881a0bb.exe"C:\Users\Admin\AppData\Local\Temp\0b508e8a07b91758e0240bb5a881a0bb.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:4256
-
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:3520