Analysis
- max time kernel
147s - max time network
158s - platform
windows10-2004_x64 - resource
win10v2004-20240226-en - resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system - submitted
02/04/2024, 10:43
Static task
static1
Behavioral task
behavioral1
Sample
f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe
Resource
win7-20240319-en
4 signatures
150 seconds
General
- Target f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe
- Size 238KB
- Sample240402-msph5sga77
- SHA256 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697
- MD5 0ce3dc374e49433d7e15d02c015e0ee3
- SHA1 71882bb02d1fa7b4a0f824afdcc1cd53bdb85ba1
- SHA512 a68b25bd8170205d491f3409393757eda6ec4c2b7f31e985b57a8d5fe9e876264167d2228087c6645ebd6dee6522386f9e39e631e6a7f06783f401432df730fa
- SSDEEP 6144:hABBPmUqO791Ou5dscGTGnbpZfcATrKTJJzM5E:hABBOa90uzVWGlRmTJX
- MD5 SHA1 SHA512 SSDEEP
Malware Config
Extracted
Family
-
vidar
C2
-
https://steamcommunity.com/profiles/76561199658817715
-
https://t.me/sa9ok
Attributes
-
user_agent
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36
Signatures
- Detect Vidar Stealer 3 IoCs
resource yara_rule behavioral2/memory/4040-4-0x0000000000400000-0x0000000000648000-memory.dmp family_vidar_v7 behavioral2/memory/4040-7-0x0000000000400000-0x0000000000648000-memory.dmp family_vidar_v7 behavioral2/memory/4040-10-0x0000000000400000-0x0000000000648000-memory.dmp family_vidar_v7 - Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3080 set thread context of 4040 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 95 - Program crash 2 IoCs
pid pid_target Process procid_target 3120 3080 WerFault.exe 84 3980 4040 WerFault.exe 95 - Suspicious use of WriteProcessMemory 28 IoCs
description pid Process procid_target PID 3080 wrote to memory of 4392 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 89 PID 3080 wrote to memory of 4392 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 89 PID 3080 wrote to memory of 4392 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 89 PID 3080 wrote to memory of 344 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 90 PID 3080 wrote to memory of 344 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 90 PID 3080 wrote to memory of 344 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 90 PID 3080 wrote to memory of 4256 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 91 PID 3080 wrote to memory of 4256 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 91 PID 3080 wrote to memory of 4256 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 91 PID 3080 wrote to memory of 4280 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 92 PID 3080 wrote to memory of 4280 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 92 PID 3080 wrote to memory of 4280 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 92 PID 3080 wrote to memory of 3972 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 93 PID 3080 wrote to memory of 3972 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 93 PID 3080 wrote to memory of 3972 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 93 PID 3080 wrote to memory of 2480 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 94 PID 3080 wrote to memory of 2480 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 94 PID 3080 wrote to memory of 2480 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 94 PID 3080 wrote to memory of 4040 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 95 PID 3080 wrote to memory of 4040 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 95 PID 3080 wrote to memory of 4040 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 95 PID 3080 wrote to memory of 4040 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 95 PID 3080 wrote to memory of 4040 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 95 PID 3080 wrote to memory of 4040 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 95 PID 3080 wrote to memory of 4040 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 95 PID 3080 wrote to memory of 4040 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 95 PID 3080 wrote to memory of 4040 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 95 PID 3080 wrote to memory of 4040 3080 f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe 95
Processes
-
C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe"C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3080 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:4392
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:344
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:4256
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:4280
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:3972
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2480
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:4040
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4040 -s 22803⤵
- Program crash
PID:3980
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3080 -s 9202⤵
- Program crash
PID:3120
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 3080 -ip 30801⤵PID:1756
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 184 -p 4040 -ip 40401⤵PID:4692