Analysis
- max time kernel
114s - max time network
149s - 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
58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe
Resource
win7-20240221-en
4 signatures
150 seconds
General
- Target 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe
- Size 234KB
- Sample240402-msmpjsfe7w
- SHA256 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff
- MD5 d0492d61a010c75b69a21b31761ac655
- SHA1 0168759aebd253fed1dd89a44d260f6eadc94a2d
- SHA512 e4552a5bcf7f6b7911a87873d6d168d44f4ab0f351c822b5ec3b14b5db359ce0fadecac7bc032111197243b79047cbe1203e4fa9afc558c9f9e2a0ecb28eb52d
- SSDEEP 6144:AhAZ0mc86LHVUCAlfzHORKOrfIrIEgcNxHookuvxNimwE5R:ImcJLHVpAl7o3rfwrYt+7/r
- 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/2824-4-0x0000000000400000-0x0000000000648000-memory.dmp family_vidar_v7 behavioral2/memory/2824-7-0x0000000000400000-0x0000000000648000-memory.dmp family_vidar_v7 behavioral2/memory/2824-9-0x0000000000400000-0x0000000000648000-memory.dmp family_vidar_v7 - Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1020 set thread context of 2824 1020 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe 99 - Program crash 2 IoCs
pid pid_target Process procid_target 2012 1020 WerFault.exe 92 4016 2824 WerFault.exe 99 - Suspicious use of WriteProcessMemory 16 IoCs
description pid Process procid_target PID 1020 wrote to memory of 4780 1020 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe 97 PID 1020 wrote to memory of 4780 1020 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe 97 PID 1020 wrote to memory of 4780 1020 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe 97 PID 1020 wrote to memory of 2944 1020 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe 98 PID 1020 wrote to memory of 2944 1020 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe 98 PID 1020 wrote to memory of 2944 1020 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe 98 PID 1020 wrote to memory of 2824 1020 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe 99 PID 1020 wrote to memory of 2824 1020 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe 99 PID 1020 wrote to memory of 2824 1020 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe 99 PID 1020 wrote to memory of 2824 1020 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe 99 PID 1020 wrote to memory of 2824 1020 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe 99 PID 1020 wrote to memory of 2824 1020 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe 99 PID 1020 wrote to memory of 2824 1020 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe 99 PID 1020 wrote to memory of 2824 1020 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe 99 PID 1020 wrote to memory of 2824 1020 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe 99 PID 1020 wrote to memory of 2824 1020 58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe 99
Processes
-
C:\Users\Admin\AppData\Local\Temp\58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe"C:\Users\Admin\AppData\Local\Temp\58c48e2b1d3d26ac96cebf8c114750582d4cdeef46a05bbf706c4b4630c541ff.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1020 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:4780
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2944
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2824
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2824 -s 23243⤵
- Program crash
PID:4016
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1020 -s 8922⤵
- Program crash
PID:2012
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 1020 -ip 10201⤵PID:1848
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 184 -p 2824 -ip 28241⤵PID:5032
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --type=utility --utility-sub-type=asset_store.mojom.AssetStoreService --lang=en-US --service-sandbox-type=asset_store_service --no-appcompat-clear --mojo-platform-channel-handle=4156 --field-trial-handle=2264,i,13734085038406049477,12426093271221802693,262144 --variations-seed-version /prefetch:81⤵PID:4228