Analysis
-
max time kernel
133s -
max time network
102s -
platform
windows10-2004_x64 -
resource
win10v2004-20240419-en -
resource tags
arch:x64arch:x86image:win10v2004-20240419-enlocale:en-usos:windows10-2004-x64system -
submitted
04-05-2024 01:14
Static task
static1
Behavioral task
behavioral1
Sample
48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe
Resource
win10v2004-20240419-en
General
-
Target
48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe
-
Size
432KB
-
MD5
7fff271b63f7af3a9a59f068a6f8955f
-
SHA1
67c0082192328a5c003efe6fd87e38802b95570d
-
SHA256
48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4
-
SHA512
55c0a315476321ea11f9696fd3642cc3bd560ce5321d3c0c0f2b6913fce11ee3d4472fef0c8ff9bdd0972ea549d5d5932a92124351cd4f3fce5524d7eb8a2346
-
SSDEEP
6144:K5/FIlRSG9VJogxAJmVku6fpAgb+K0iudeI9Iaf3PMFViAnHo:w/FIbxAkV1gb7ZuwIaafP0Ho
Malware Config
Extracted
stealc
Extracted
vidar
9.3
03cea2609023d13f145ac6c5dc897112
https://steamcommunity.com/profiles/76561199680449169
https://t.me/r1g1o
-
profile_id_v2
03cea2609023d13f145ac6c5dc897112
-
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 4 IoCs
Processes:
resource yara_rule behavioral2/memory/4280-1-0x0000000000400000-0x0000000000643000-memory.dmp family_vidar_v7 behavioral2/memory/552-2-0x0000000000940000-0x00000000009A2FAE-memory.dmp family_vidar_v7 behavioral2/memory/4280-4-0x0000000000400000-0x0000000000643000-memory.dmp family_vidar_v7 behavioral2/memory/4280-6-0x0000000000400000-0x0000000000643000-memory.dmp family_vidar_v7 -
Detects Windows executables referencing non-Windows User-Agents 4 IoCs
Processes:
resource yara_rule behavioral2/memory/4280-1-0x0000000000400000-0x0000000000643000-memory.dmp INDICATOR_SUSPICIOUS_EXE_NoneWindowsUA behavioral2/memory/552-2-0x0000000000940000-0x00000000009A2FAE-memory.dmp INDICATOR_SUSPICIOUS_EXE_NoneWindowsUA behavioral2/memory/4280-4-0x0000000000400000-0x0000000000643000-memory.dmp INDICATOR_SUSPICIOUS_EXE_NoneWindowsUA behavioral2/memory/4280-6-0x0000000000400000-0x0000000000643000-memory.dmp INDICATOR_SUSPICIOUS_EXE_NoneWindowsUA -
Detects binaries and memory artifacts referencing sandbox DLLs typically observed in sandbox evasion 4 IoCs
Processes:
resource yara_rule behavioral2/memory/4280-1-0x0000000000400000-0x0000000000643000-memory.dmp INDICATOR_SUSPICIOUS_EXE_SandboxHookingDLL behavioral2/memory/552-2-0x0000000000940000-0x00000000009A2FAE-memory.dmp INDICATOR_SUSPICIOUS_EXE_SandboxHookingDLL behavioral2/memory/4280-4-0x0000000000400000-0x0000000000643000-memory.dmp INDICATOR_SUSPICIOUS_EXE_SandboxHookingDLL behavioral2/memory/4280-6-0x0000000000400000-0x0000000000643000-memory.dmp INDICATOR_SUSPICIOUS_EXE_SandboxHookingDLL -
Detects executables containing potential Windows Defender anti-emulation checks 4 IoCs
Processes:
resource yara_rule behavioral2/memory/4280-1-0x0000000000400000-0x0000000000643000-memory.dmp INDICATOR_SUSPICIOUS_EXE_WindDefender_AntiEmaulation behavioral2/memory/552-2-0x0000000000940000-0x00000000009A2FAE-memory.dmp INDICATOR_SUSPICIOUS_EXE_WindDefender_AntiEmaulation behavioral2/memory/4280-4-0x0000000000400000-0x0000000000643000-memory.dmp INDICATOR_SUSPICIOUS_EXE_WindDefender_AntiEmaulation behavioral2/memory/4280-6-0x0000000000400000-0x0000000000643000-memory.dmp INDICATOR_SUSPICIOUS_EXE_WindDefender_AntiEmaulation -
Suspicious use of SetThreadContext 1 IoCs
Processes:
48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exedescription pid process target process PID 552 set thread context of 4280 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 4272 4280 WerFault.exe RegAsm.exe -
Suspicious use of WriteProcessMemory 18 IoCs
Processes:
48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exedescription pid process target process PID 552 wrote to memory of 1500 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe PID 552 wrote to memory of 1500 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe PID 552 wrote to memory of 1500 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe PID 552 wrote to memory of 4852 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe PID 552 wrote to memory of 4852 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe PID 552 wrote to memory of 4852 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe PID 552 wrote to memory of 4592 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe PID 552 wrote to memory of 4592 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe PID 552 wrote to memory of 4592 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe PID 552 wrote to memory of 4280 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe PID 552 wrote to memory of 4280 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe PID 552 wrote to memory of 4280 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe PID 552 wrote to memory of 4280 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe PID 552 wrote to memory of 4280 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe PID 552 wrote to memory of 4280 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe PID 552 wrote to memory of 4280 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe PID 552 wrote to memory of 4280 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe PID 552 wrote to memory of 4280 552 48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe RegAsm.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe"C:\Users\Admin\AppData\Local\Temp\48a6d2eb28127d8bc1623400f0b33ea5f51a7473ce3369a14e8b4a5f0d02bca4.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4280 -s 21763⤵
- Program crash
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 4280 -ip 42801⤵
Network
MITRE ATT&CK Matrix
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/552-0-0x000000000099E000-0x00000000009A0000-memory.dmpFilesize
8KB
-
memory/552-2-0x0000000000940000-0x00000000009A2FAE-memory.dmpFilesize
395KB
-
memory/4280-1-0x0000000000400000-0x0000000000643000-memory.dmpFilesize
2.3MB
-
memory/4280-4-0x0000000000400000-0x0000000000643000-memory.dmpFilesize
2.3MB
-
memory/4280-6-0x0000000000400000-0x0000000000643000-memory.dmpFilesize
2.3MB