Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
141s -
max time network
122s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
05/03/2024, 14:46
Behavioral task
behavioral1
Sample
b4f52848c48aea663e5344e33a1b087a.exe
Resource
win7-20240221-en
5 signatures
150 seconds
Behavioral task
behavioral2
Sample
b4f52848c48aea663e5344e33a1b087a.exe
Resource
win10v2004-20240226-en
8 signatures
150 seconds
General
-
Target
b4f52848c48aea663e5344e33a1b087a.exe
-
Size
609KB
-
MD5
b4f52848c48aea663e5344e33a1b087a
-
SHA1
952e076be5498fcbb41123070c5a297c329e2395
-
SHA256
25510d20b983dbfc0443684dd1674192cb32b9ab06a2ab9e67e2db6f99ead154
-
SHA512
5e78c19e2084ae3c9f90be86e4458ded13cea66f2185bc26637a2b00f8ff57d5d1da09ed99f47b981e59815ef63ee7d10ffb506157b178e95fa56356e8dc997e
-
SSDEEP
12288:BLcKp2Adls/rnjs7RLKslAmJSv4KMwUU9d8Kb6a:CK2GsD4RLTlzJSv4sGKGa
Score
7/10
Malware Config
Signatures
-
resource yara_rule behavioral1/memory/2164-0-0x0000000000400000-0x0000000000437000-memory.dmp upx behavioral1/memory/2164-5-0x0000000000400000-0x0000000000437000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2164 set thread context of 2080 2164 b4f52848c48aea663e5344e33a1b087a.exe 28 -
Program crash 1 IoCs
pid pid_target Process procid_target 2172 2080 WerFault.exe 28 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 2164 b4f52848c48aea663e5344e33a1b087a.exe -
Suspicious use of WriteProcessMemory 13 IoCs
description pid Process procid_target PID 2164 wrote to memory of 2080 2164 b4f52848c48aea663e5344e33a1b087a.exe 28 PID 2164 wrote to memory of 2080 2164 b4f52848c48aea663e5344e33a1b087a.exe 28 PID 2164 wrote to memory of 2080 2164 b4f52848c48aea663e5344e33a1b087a.exe 28 PID 2164 wrote to memory of 2080 2164 b4f52848c48aea663e5344e33a1b087a.exe 28 PID 2164 wrote to memory of 2080 2164 b4f52848c48aea663e5344e33a1b087a.exe 28 PID 2164 wrote to memory of 2080 2164 b4f52848c48aea663e5344e33a1b087a.exe 28 PID 2164 wrote to memory of 2080 2164 b4f52848c48aea663e5344e33a1b087a.exe 28 PID 2164 wrote to memory of 2080 2164 b4f52848c48aea663e5344e33a1b087a.exe 28 PID 2164 wrote to memory of 2080 2164 b4f52848c48aea663e5344e33a1b087a.exe 28 PID 2080 wrote to memory of 2172 2080 b4f52848c48aea663e5344e33a1b087a.exe 29 PID 2080 wrote to memory of 2172 2080 b4f52848c48aea663e5344e33a1b087a.exe 29 PID 2080 wrote to memory of 2172 2080 b4f52848c48aea663e5344e33a1b087a.exe 29 PID 2080 wrote to memory of 2172 2080 b4f52848c48aea663e5344e33a1b087a.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\b4f52848c48aea663e5344e33a1b087a.exe"C:\Users\Admin\AppData\Local\Temp\b4f52848c48aea663e5344e33a1b087a.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2164 -
C:\Users\Admin\AppData\Local\Temp\b4f52848c48aea663e5344e33a1b087a.exeC:\Users\Admin\AppData\Local\Temp\b4f52848c48aea663e5344e33a1b087a.exe2⤵
- Suspicious use of WriteProcessMemory
PID:2080 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2080 -s 1283⤵
- Program crash
PID:2172
-
-