Analysis
- max time kernel
95s - max time network
137s - platform
windows10-2004_x64 - resource
win10v2004-20240412-en - resource tags
arch:x64arch:x86image:win10v2004-20240412-enlocale:en-usos:windows10-2004-x64system - submitted
17/04/2024, 13:53
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe
Resource
win7-20240221-en
6 signatures
150 seconds
Behavioral task
behavioral2
Sample
5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe
Resource
win10v2004-20240412-en
5 signatures
150 seconds
General
- Target 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe
- Size 224KB
- Sample240417-q7ffkaaf38
- SHA256 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e
- MD5 769c8ad3f187882a49cda5d26103730c
- SHA1 dae972d44336ffbb28509eabe946e83972166502
- SHA512 08a5f80741ea4b0325efe15ad69feb44f4ea1a8ace70f072109f4ec19ad4bc56185aa5f3f734b03906ad3691f9cae43aea3a4ba88e507f97a753e11ca913669c
- SSDEEP 3072:Q52Gig7F8wUC1mK2iKkb8YxhX7EQXdeBvR/P4ieqSgvBEn/zcAGqxp6qUDbKSB/:sdF8l9sKqHbYQU/BSg5En/zqq/6qU/
- MD5 SHA1 SHA512 SSDEEP
Score
10/10
Malware Config
Extracted
Family
-
vidar
Version
-
8.5
Botnet
-
e1d2225c9e4727fe2818a17924d7e065
C2
-
https://steamcommunity.com/profiles/76561199658817715
-
https://t.me/sa9ok
Attributes
-
profile_id_v2
e1d2225c9e4727fe2818a17924d7e065
-
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/3520-4-0x0000000000400000-0x0000000000644000-memory.dmp family_vidar_v7 behavioral2/memory/3520-12-0x0000000000400000-0x0000000000644000-memory.dmp family_vidar_v7 behavioral2/memory/3520-7-0x0000000000400000-0x0000000000644000-memory.dmp family_vidar_v7 - Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 628 set thread context of 3520 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 87 - Program crash 1 IoCs
pid pid_target Process procid_target 4980 3520 WerFault.exe 87 - Suspicious use of WriteProcessMemory 19 IoCs
description pid Process procid_target PID 628 wrote to memory of 1272 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 84 PID 628 wrote to memory of 1272 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 84 PID 628 wrote to memory of 1272 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 84 PID 628 wrote to memory of 2352 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 85 PID 628 wrote to memory of 2352 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 85 PID 628 wrote to memory of 2352 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 85 PID 628 wrote to memory of 2984 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 86 PID 628 wrote to memory of 2984 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 86 PID 628 wrote to memory of 2984 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 86 PID 628 wrote to memory of 3520 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 87 PID 628 wrote to memory of 3520 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 87 PID 628 wrote to memory of 3520 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 87 PID 628 wrote to memory of 3520 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 87 PID 628 wrote to memory of 3520 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 87 PID 628 wrote to memory of 3520 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 87 PID 628 wrote to memory of 3520 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 87 PID 628 wrote to memory of 3520 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 87 PID 628 wrote to memory of 3520 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 87 PID 628 wrote to memory of 3520 628 5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe 87
Processes
-
C:\Users\Admin\AppData\Local\Temp\5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe"C:\Users\Admin\AppData\Local\Temp\5230c370cbdb95a2f4a30e70b7ac6a857af81c9498ef473704778fe86e6dbe1e.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:628 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:1272
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2352
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2984
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:3520
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3520 -s 23363⤵
- Program crash
PID:4980
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 3520 -ip 35201⤵PID:2336