Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
149s -
max time network
152s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
11/05/2024, 06:58
Static task
static1
Behavioral task
behavioral1
Sample
9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe
Resource
win10v2004-20240508-en
General
-
Target
9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe
-
Size
363KB
-
MD5
ea0081722a86c3016aa249262483c7ca
-
SHA1
c6fe97dc6211dcbd732619a11f7a525b800765e4
-
SHA256
9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8
-
SHA512
e03e5077b5ecd2991e87589f133c84a991853caf507476d6b385a2977789296225cce347d71fe836a03fccf71054d56e24cdc8bd4aeee6e1bb0f14e624cf3089
-
SSDEEP
6144:pZPllhS4qdxjPxUUsTl0+ruzXgU+t8YY6FZZFWKM+MsMk91EknZcHZmmKU:zt/SNRezujgUM8YhPFWKM+MsMaVZcHxh
Malware Config
Extracted
stealc
Extracted
vidar
9.6
681a223bec180ebfdc48547d3d5bd784
https://steamcommunity.com/profiles/76561199681720597
https://t.me/talmatin
-
profile_id_v2
681a223bec180ebfdc48547d3d5bd784
-
user_agent
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 OPR/101.0.0.0
Signatures
-
Detect Vidar Stealer 3 IoCs
resource yara_rule behavioral2/memory/3104-1-0x0000000000400000-0x0000000000647000-memory.dmp family_vidar_v7 behavioral2/memory/3104-3-0x0000000000400000-0x0000000000647000-memory.dmp family_vidar_v7 behavioral2/memory/3104-5-0x0000000000400000-0x0000000000647000-memory.dmp family_vidar_v7 -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 800 set thread context of 3104 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 91 -
Program crash 1 IoCs
pid pid_target Process procid_target 1428 3104 WerFault.exe 91 -
Suspicious use of WriteProcessMemory 24 IoCs
description pid Process procid_target PID 800 wrote to memory of 3732 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 86 PID 800 wrote to memory of 3732 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 86 PID 800 wrote to memory of 3732 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 86 PID 800 wrote to memory of 388 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 87 PID 800 wrote to memory of 388 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 87 PID 800 wrote to memory of 388 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 87 PID 800 wrote to memory of 2972 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 88 PID 800 wrote to memory of 2972 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 88 PID 800 wrote to memory of 2972 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 88 PID 800 wrote to memory of 4248 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 89 PID 800 wrote to memory of 4248 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 89 PID 800 wrote to memory of 4248 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 89 PID 800 wrote to memory of 3492 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 90 PID 800 wrote to memory of 3492 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 90 PID 800 wrote to memory of 3492 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 90 PID 800 wrote to memory of 3104 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 91 PID 800 wrote to memory of 3104 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 91 PID 800 wrote to memory of 3104 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 91 PID 800 wrote to memory of 3104 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 91 PID 800 wrote to memory of 3104 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 91 PID 800 wrote to memory of 3104 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 91 PID 800 wrote to memory of 3104 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 91 PID 800 wrote to memory of 3104 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 91 PID 800 wrote to memory of 3104 800 9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe 91
Processes
-
C:\Users\Admin\AppData\Local\Temp\9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe"C:\Users\Admin\AppData\Local\Temp\9ca6f73f7f915ad1b27b1e3901c5d89ff829f9cd146812077fa1c2e295338ce8.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:800 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:3732
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:388
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2972
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:4248
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:3492
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:3104
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3104 -s 22683⤵
- Program crash
PID:1428
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 3104 -ip 31041⤵PID:4692