Analysis
- max time kernel
140s - max time network
128s - platform
windows10-2004_x64 - resource
win10v2004-20240508-en - resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system - submitted
17/05/2024, 16:08
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
a2f94952c89ea440f82877365db5b4a5cf14a10e4168a22a92fce4a8fd98404f.exe
Resource
win7-20240220-en
2 signatures
150 seconds
General
- Target a2f94952c89ea440f82877365db5b4a5cf14a10e4168a22a92fce4a8fd98404f.exe
- Size 363KB
- Sample240517-tk9bxafe78
- SHA256 a2f94952c89ea440f82877365db5b4a5cf14a10e4168a22a92fce4a8fd98404f
- MD5 75db6dfdebb9bf0d98acfc15f2219c62
- SHA1 5bc1ceec4269b4e893f2b00c1c4b3c0cb42a3291
- SHA512 b295c110369cb2c56d87aab45ff93961b076474d16ca9a7138ab3e6e7acbc8a13a2949dcbc88e6f2e96e4fae793e1793b3052c7ec390ee3d6cd517029583dd2f
- SSDEEP 6144:1JhLSp8zWMtAJA0Z9aRlEiw+pVc4Amr7me33k/JNSdiaJIlsZa6n:pLSpmqKRw+84B7mA3aJE4aOAFn
- MD5 SHA1 SHA512 SSDEEP
Malware Config
Extracted
Family
-
stealc
rc4.plain
Signatures
- Detect Vidar Stealer 11 IoCs
resource yara_rule behavioral2/memory/4356-2-0x0000000000400000-0x0000000000646000-memory.dmp family_vidar_v7 behavioral2/memory/4356-5-0x0000000000400000-0x0000000000646000-memory.dmp family_vidar_v7 behavioral2/memory/4356-7-0x0000000000400000-0x0000000000646000-memory.dmp family_vidar_v7 behavioral2/memory/4356-14-0x0000000000400000-0x0000000000646000-memory.dmp family_vidar_v7 behavioral2/memory/4356-15-0x0000000000400000-0x0000000000646000-memory.dmp family_vidar_v7 behavioral2/memory/4356-32-0x0000000000400000-0x0000000000646000-memory.dmp family_vidar_v7 behavioral2/memory/4356-33-0x0000000000400000-0x0000000000646000-memory.dmp family_vidar_v7 behavioral2/memory/4356-49-0x0000000000400000-0x0000000000646000-memory.dmp family_vidar_v7 behavioral2/memory/4356-50-0x0000000000400000-0x0000000000646000-memory.dmp family_vidar_v7 behavioral2/memory/4356-67-0x0000000000400000-0x0000000000646000-memory.dmp family_vidar_v7 behavioral2/memory/4356-68-0x0000000000400000-0x0000000000646000-memory.dmp family_vidar_v7 - Downloads MZ/PE file
- Checks computer location settings 2 TTPs 1 IoCs
Looks up country code configured in the registry, likely geofence.
description ioc Process Key value queried \REGISTRY\USER\S-1-5-21-4124900551-4068476067-3491212533-1000\Control Panel\International\Geo\Nation RegAsm.exe - Reads data files stored by FTP clients 2 TTPs
Tries to access configuration files associated with programs like FileZilla.
- Reads user/profile data of local email clients 2 TTPs
Email clients store some user data on disk where infostealers will often target it.
- Reads user/profile data of web browsers 2 TTPs
Infostealers often target stored browser data, which can include saved credentials etc.
- Accesses cryptocurrency files/wallets, possible credential harvesting 2 TTPs
- Checks installed software on the system 1 TTPs
Looks up Uninstall key entries in the registry to enumerate software on the system.
- Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3364 set thread context of 4356 3364 a2f94952c89ea440f82877365db5b4a5cf14a10e4168a22a92fce4a8fd98404f.exe 84 - Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
- Checks processor information in registry 2 TTPs 1 IoCs
Processor information is often read in order to detect sandboxing environments.
description ioc Process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString RegAsm.exe - Delays execution with timeout.exe 1 IoCs
pid Process 636 timeout.exe - Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 4356 RegAsm.exe 4356 RegAsm.exe 4356 RegAsm.exe 4356 RegAsm.exe - Suspicious use of WriteProcessMemory 15 IoCs
description pid Process procid_target PID 3364 wrote to memory of 4356 3364 a2f94952c89ea440f82877365db5b4a5cf14a10e4168a22a92fce4a8fd98404f.exe 84 PID 3364 wrote to memory of 4356 3364 a2f94952c89ea440f82877365db5b4a5cf14a10e4168a22a92fce4a8fd98404f.exe 84 PID 3364 wrote to memory of 4356 3364 a2f94952c89ea440f82877365db5b4a5cf14a10e4168a22a92fce4a8fd98404f.exe 84 PID 3364 wrote to memory of 4356 3364 a2f94952c89ea440f82877365db5b4a5cf14a10e4168a22a92fce4a8fd98404f.exe 84 PID 3364 wrote to memory of 4356 3364 a2f94952c89ea440f82877365db5b4a5cf14a10e4168a22a92fce4a8fd98404f.exe 84 PID 3364 wrote to memory of 4356 3364 a2f94952c89ea440f82877365db5b4a5cf14a10e4168a22a92fce4a8fd98404f.exe 84 PID 3364 wrote to memory of 4356 3364 a2f94952c89ea440f82877365db5b4a5cf14a10e4168a22a92fce4a8fd98404f.exe 84 PID 3364 wrote to memory of 4356 3364 a2f94952c89ea440f82877365db5b4a5cf14a10e4168a22a92fce4a8fd98404f.exe 84 PID 3364 wrote to memory of 4356 3364 a2f94952c89ea440f82877365db5b4a5cf14a10e4168a22a92fce4a8fd98404f.exe 84 PID 4356 wrote to memory of 4496 4356 RegAsm.exe 98 PID 4356 wrote to memory of 4496 4356 RegAsm.exe 98 PID 4356 wrote to memory of 4496 4356 RegAsm.exe 98 PID 4496 wrote to memory of 636 4496 cmd.exe 100 PID 4496 wrote to memory of 636 4496 cmd.exe 100 PID 4496 wrote to memory of 636 4496 cmd.exe 100
Processes
-
C:\Users\Admin\AppData\Local\Temp\a2f94952c89ea440f82877365db5b4a5cf14a10e4168a22a92fce4a8fd98404f.exe"C:\Users\Admin\AppData\Local\Temp\a2f94952c89ea440f82877365db5b4a5cf14a10e4168a22a92fce4a8fd98404f.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3364 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵
- Checks computer location settings
- Checks processor information in registry
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:4356 -
C:\Windows\SysWOW64\cmd.exe"C:\Windows\System32\cmd.exe" /c timeout /t 10 & rd /s /q "C:\ProgramData\HIDGCFBFBFBK" & exit3⤵
- Suspicious use of WriteProcessMemory
PID:4496 -
C:\Windows\SysWOW64\timeout.exetimeout /t 104⤵
- Delays execution with timeout.exe
PID:636
-
-
-