Analysis
- max time kernel
134s - max time network
299s - platform
windows10-1703_x64 - resource
win10-20240404-en - resource tags
arch:x64arch:x86image:win10-20240404-enlocale:en-usos:windows10-1703-x64system - submitted
17/06/2024, 05:08
Static task
static1
Behavioral task
behavioral1
Sample
a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe
Resource
win7-20240508-en
General
- Target a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe
- Size 435KB
- Sample240617-fsx2yszdml
- SHA256 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329
- MD5 9e49e965497860a4ea1e4065afad6304
- SHA1 aff9631611d09814d7acd75b3ee18b50ea074e2d
- SHA512 bdd24dee78518ae709e061ac6f7761f76e59c0013876b5076c2648e6f531f253e5d507dd2629352bd4dd8fad8bacbd4458576a6f451f87ab4db203f97605e06f
- SSDEEP 6144:0S1gnkIzWbaEBCS2Ra43A2khln30krfESFDhORgYzUQMnlw9NPNDL5NXPMPvnT2Y:0IgnkIzcRYkrfDXCgYwnlwD1fMPvyaH
- MD5 SHA1 SHA512 SSDEEP
Malware Config
Extracted
-
stealc
Extracted
-
vidar
-
https://t.me/memve4erin
-
https://steamcommunity.com/profiles/76561199699680841
-
user_agent
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:129.0) Gecko/20100101 Firefox/129.0
Signatures
- Detect Vidar Stealer 9 IoCs
resource yara_rule behavioral2/memory/3028-1-0x0000000000400000-0x0000000000648000-memory.dmp family_vidar_v7 behavioral2/memory/3028-4-0x0000000000400000-0x0000000000648000-memory.dmp family_vidar_v7 behavioral2/memory/3028-5-0x0000000000400000-0x0000000000648000-memory.dmp family_vidar_v7 behavioral2/memory/3028-20-0x0000000000400000-0x0000000000648000-memory.dmp family_vidar_v7 behavioral2/memory/3028-21-0x0000000000400000-0x0000000000648000-memory.dmp family_vidar_v7 behavioral2/memory/3028-38-0x0000000000400000-0x0000000000648000-memory.dmp family_vidar_v7 behavioral2/memory/3028-39-0x0000000000400000-0x0000000000648000-memory.dmp family_vidar_v7 behavioral2/memory/3028-51-0x0000000000400000-0x0000000000648000-memory.dmp family_vidar_v7 behavioral2/memory/3028-52-0x0000000000400000-0x0000000000648000-memory.dmp family_vidar_v7 - Downloads MZ/PE file
- 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 3080 set thread context of 3028 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 77 - Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
- Program crash 1 IoCs
pid pid_target Process procid_target 3784 3080 WerFault.exe 72 - 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 3476 timeout.exe - Suspicious behavior: EnumeratesProcesses 10 IoCs
pid Process 3028 RegAsm.exe 3028 RegAsm.exe 3028 RegAsm.exe 3028 RegAsm.exe 3028 RegAsm.exe 3028 RegAsm.exe 3028 RegAsm.exe 3028 RegAsm.exe 3028 RegAsm.exe 3028 RegAsm.exe - Suspicious use of WriteProcessMemory 27 IoCs
description pid Process procid_target PID 3080 wrote to memory of 492 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 73 PID 3080 wrote to memory of 492 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 73 PID 3080 wrote to memory of 492 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 73 PID 3080 wrote to memory of 4316 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 74 PID 3080 wrote to memory of 4316 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 74 PID 3080 wrote to memory of 4316 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 74 PID 3080 wrote to memory of 3628 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 75 PID 3080 wrote to memory of 3628 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 75 PID 3080 wrote to memory of 3628 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 75 PID 3080 wrote to memory of 3560 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 76 PID 3080 wrote to memory of 3560 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 76 PID 3080 wrote to memory of 3560 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 76 PID 3080 wrote to memory of 3028 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 77 PID 3080 wrote to memory of 3028 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 77 PID 3080 wrote to memory of 3028 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 77 PID 3080 wrote to memory of 3028 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 77 PID 3080 wrote to memory of 3028 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 77 PID 3080 wrote to memory of 3028 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 77 PID 3080 wrote to memory of 3028 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 77 PID 3080 wrote to memory of 3028 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 77 PID 3080 wrote to memory of 3028 3080 a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe 77 PID 3028 wrote to memory of 2440 3028 RegAsm.exe 81 PID 3028 wrote to memory of 2440 3028 RegAsm.exe 81 PID 3028 wrote to memory of 2440 3028 RegAsm.exe 81 PID 2440 wrote to memory of 3476 2440 cmd.exe 83 PID 2440 wrote to memory of 3476 2440 cmd.exe 83 PID 2440 wrote to memory of 3476 2440 cmd.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.exe"C:\Users\Admin\AppData\Local\Temp\a6aa41c4146d958de74395c388ef2af7cc1b47c381c8d4661130d510143e7329.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:492
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:4316
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:3628
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:3560
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵
- Checks processor information in registry
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:3028 -
C:\Windows\SysWOW64\cmd.exe"C:\Windows\System32\cmd.exe" /c timeout /t 10 & rd /s /q "C:\ProgramData\AEGHJKJKKJDH" & exit3⤵
- Suspicious use of WriteProcessMemory
PID:2440 -
C:\Windows\SysWOW64\timeout.exetimeout /t 104⤵
- Delays execution with timeout.exe
PID:3476
-
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3080 -s 3202⤵
- Program crash
PID:3784
-