Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
148s -
max time network
150s -
platform
windows10-2004_x64 -
resource
win10v2004-20241007-en -
resource tags
arch:x64arch:x86image:win10v2004-20241007-enlocale:en-usos:windows10-2004-x64system -
submitted
22/01/2025, 02:44
Static task
static1
Behavioral task
behavioral1
Sample
72fa904d41cfc7c04d3c095e84449aecb989cc98b1d008b3ce9b51717173b053.exe
Resource
win7-20240903-en
Behavioral task
behavioral2
Sample
72fa904d41cfc7c04d3c095e84449aecb989cc98b1d008b3ce9b51717173b053.exe
Resource
win10v2004-20241007-en
General
-
Target
72fa904d41cfc7c04d3c095e84449aecb989cc98b1d008b3ce9b51717173b053.exe
-
Size
713KB
-
MD5
5006219231a8cb74552d0ad9c1b02ae9
-
SHA1
1b54149f1d9c54d370c37fc00ad2e28642059c74
-
SHA256
72fa904d41cfc7c04d3c095e84449aecb989cc98b1d008b3ce9b51717173b053
-
SHA512
3a71ab78c5ad20325752a4e25267ba086e845cbbdd0452c138a9ac2367f7f5c181d9d1e2019307b4687a170b5ca212559ebe06c44fa43289ba8cdcfaef6a8a0d
-
SSDEEP
12288:IPHkO6/ceaCdAA3w9zyaZyKgrwoyIgXCYAMA7Q:IPHkOXgAj9zVZgZDd7Q
Malware Config
Extracted
vipkeylogger
https://api.telegram.org/bot7965348925:AAGe8wdrvk9A3lxr1GIjGigodJ_zZ7prhfs/sendMessage?chat_id=6848903538
Signatures
-
VIPKeylogger
VIPKeylogger is a keylogger and infostealer written in C# and it resembles SnakeKeylogger that was found in 2020.
-
Vipkeylogger family
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1724 set thread context of 3400 1724 72fa904d41cfc7c04d3c095e84449aecb989cc98b1d008b3ce9b51717173b053.exe 83 -
Program crash 1 IoCs
pid pid_target Process procid_target 4344 3400 WerFault.exe 83 -
Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 1724 wrote to memory of 3400 1724 72fa904d41cfc7c04d3c095e84449aecb989cc98b1d008b3ce9b51717173b053.exe 83 PID 1724 wrote to memory of 3400 1724 72fa904d41cfc7c04d3c095e84449aecb989cc98b1d008b3ce9b51717173b053.exe 83 PID 1724 wrote to memory of 3400 1724 72fa904d41cfc7c04d3c095e84449aecb989cc98b1d008b3ce9b51717173b053.exe 83 PID 1724 wrote to memory of 3400 1724 72fa904d41cfc7c04d3c095e84449aecb989cc98b1d008b3ce9b51717173b053.exe 83 PID 1724 wrote to memory of 3400 1724 72fa904d41cfc7c04d3c095e84449aecb989cc98b1d008b3ce9b51717173b053.exe 83 PID 1724 wrote to memory of 3400 1724 72fa904d41cfc7c04d3c095e84449aecb989cc98b1d008b3ce9b51717173b053.exe 83 PID 1724 wrote to memory of 3400 1724 72fa904d41cfc7c04d3c095e84449aecb989cc98b1d008b3ce9b51717173b053.exe 83 PID 1724 wrote to memory of 3400 1724 72fa904d41cfc7c04d3c095e84449aecb989cc98b1d008b3ce9b51717173b053.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\72fa904d41cfc7c04d3c095e84449aecb989cc98b1d008b3ce9b51717173b053.exe"C:\Users\Admin\AppData\Local\Temp\72fa904d41cfc7c04d3c095e84449aecb989cc98b1d008b3ce9b51717173b053.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1724 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AddInProcess32.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AddInProcess32.exe"2⤵PID:3400
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3400 -s 683⤵
- Program crash
PID:4344
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 3400 -ip 34001⤵PID:2256