Malware Analysis Report

2025-08-11 00:37

Sample ID 240331-bdakwsbd26
Target 0ce3dc374e49433d7e15d02c015e0ee3.bin
SHA256 45ef4d31ac4a75a0cdb16cf4d4a2a7040b3bd03682569c91a67cc0a4f2c8811b
Tags
vidar stealer
score
10/10

Table of Contents

Analysis Overview

MITRE ATT&CK

Analysis: static1

Detonation Overview

Signatures

Analysis: behavioral1

Detonation Overview

Command Line

Signatures

Processes

Network

Files

Analysis: behavioral2

Detonation Overview

Command Line

Signatures

Processes

Network

Files

Analysis Overview

score
10/10

SHA256

45ef4d31ac4a75a0cdb16cf4d4a2a7040b3bd03682569c91a67cc0a4f2c8811b

Threat Level: Known bad

The file 0ce3dc374e49433d7e15d02c015e0ee3.bin was found to be: Known bad.

Malicious Activity Summary

vidar stealer

Detect Vidar Stealer

Vidar

Suspicious use of SetThreadContext

Program crash

Suspicious use of WriteProcessMemory

MITRE ATT&CK

N/A

Analysis: static1

Detonation Overview

Reported

2024-03-31 01:01

Signatures

N/A

Analysis: behavioral1

Detonation Overview

Submitted

2024-03-31 01:01

Reported

2024-03-31 01:03

Platform

win7-20240221-en

Max time kernel

117s

Max time network

119s

Command Line

"C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe"

Signatures

Suspicious use of WriteProcessMemory

Description Indicator Process Target
PID 2168 wrote to memory of 3036 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 2168 wrote to memory of 3036 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 2168 wrote to memory of 3036 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 2168 wrote to memory of 3036 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 2168 wrote to memory of 3036 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 2168 wrote to memory of 3036 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 2168 wrote to memory of 3036 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 2168 wrote to memory of 3036 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 2168 wrote to memory of 2492 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\SysWOW64\WerFault.exe
PID 2168 wrote to memory of 2492 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\SysWOW64\WerFault.exe
PID 2168 wrote to memory of 2492 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\SysWOW64\WerFault.exe
PID 2168 wrote to memory of 2492 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\SysWOW64\WerFault.exe

Processes

C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe

"C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe"

C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe

"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"

C:\Windows\SysWOW64\WerFault.exe

C:\Windows\SysWOW64\WerFault.exe -u -p 2168 -s 504

Network

N/A

Files

memory/2168-0-0x00000000012E0000-0x000000000131E000-memory.dmp

memory/2168-1-0x00000000743E0000-0x0000000074ACE000-memory.dmp

memory/2168-4-0x0000000002720000-0x0000000004720000-memory.dmp

memory/3036-5-0x0000000000400000-0x0000000000648000-memory.dmp

memory/3036-7-0x0000000000400000-0x0000000000648000-memory.dmp

memory/2168-9-0x00000000743E0000-0x0000000074ACE000-memory.dmp

memory/2168-10-0x0000000002720000-0x0000000004720000-memory.dmp

Analysis: behavioral2

Detonation Overview

Submitted

2024-03-31 01:01

Reported

2024-03-31 01:04

Platform

win10v2004-20240226-en

Max time kernel

144s

Max time network

161s

Command Line

"C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe"

Signatures

Detect Vidar Stealer

stealer
Description Indicator Process Target
N/A N/A N/A N/A
N/A N/A N/A N/A
N/A N/A N/A N/A

Vidar

stealer vidar

Suspicious use of SetThreadContext

Description Indicator Process Target
PID 1844 set thread context of 2388 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe

Suspicious use of WriteProcessMemory

Description Indicator Process Target
PID 1844 wrote to memory of 2504 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 1844 wrote to memory of 2504 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 1844 wrote to memory of 2504 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 1844 wrote to memory of 2388 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 1844 wrote to memory of 2388 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 1844 wrote to memory of 2388 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 1844 wrote to memory of 2388 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 1844 wrote to memory of 2388 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 1844 wrote to memory of 2388 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 1844 wrote to memory of 2388 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 1844 wrote to memory of 2388 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 1844 wrote to memory of 2388 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
PID 1844 wrote to memory of 2388 N/A C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe

Processes

C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe

"C:\Users\Admin\AppData\Local\Temp\f714adc256ed7b0d48a50c9b10d0db1d6285541801e720569c86fceeba072697.exe"

C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe

"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"

C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe

"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"

C:\Windows\SysWOW64\WerFault.exe

C:\Windows\SysWOW64\WerFault.exe -pss -s 452 -p 1844 -ip 1844

C:\Windows\SysWOW64\WerFault.exe

C:\Windows\SysWOW64\WerFault.exe -u -p 1844 -s 884

C:\Windows\SysWOW64\WerFault.exe

C:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 2388 -ip 2388

C:\Windows\SysWOW64\WerFault.exe

C:\Windows\SysWOW64\WerFault.exe -u -p 2388 -s 2248

Network

Country Destination Domain Proto
US 8.8.8.8:53 241.150.49.20.in-addr.arpa udp
US 8.8.8.8:53 240.221.184.93.in-addr.arpa udp
US 8.8.8.8:53 steamcommunity.com udp
GB 104.82.234.109:443 steamcommunity.com tcp
US 8.8.8.8:53 109.234.82.104.in-addr.arpa udp
DE 78.47.221.177:443 78.47.221.177 tcp
US 8.8.8.8:53 177.221.47.78.in-addr.arpa udp
DE 78.47.221.177:443 78.47.221.177 tcp
DE 78.47.221.177:443 78.47.221.177 tcp
US 8.8.8.8:53 23.159.190.20.in-addr.arpa udp
US 8.8.8.8:53 58.55.71.13.in-addr.arpa udp
DE 78.47.221.177:443 78.47.221.177 tcp
US 8.8.8.8:53 26.165.165.52.in-addr.arpa udp
US 8.8.8.8:53 18.31.95.13.in-addr.arpa udp
US 8.8.8.8:53 18.134.221.88.in-addr.arpa udp
US 8.8.8.8:53 149.220.183.52.in-addr.arpa udp
US 8.8.8.8:53 217.106.137.52.in-addr.arpa udp
US 8.8.8.8:53 92.16.208.104.in-addr.arpa udp

Files

memory/1844-0-0x0000000000A80000-0x0000000000ABE000-memory.dmp

memory/1844-1-0x0000000074520000-0x0000000074CD0000-memory.dmp

memory/2388-4-0x0000000000400000-0x0000000000648000-memory.dmp

memory/2388-7-0x0000000000400000-0x0000000000648000-memory.dmp

memory/2388-9-0x0000000000400000-0x0000000000648000-memory.dmp

memory/1844-10-0x0000000002F70000-0x0000000004F70000-memory.dmp

memory/1844-14-0x0000000074520000-0x0000000074CD0000-memory.dmp

memory/1844-15-0x0000000002F70000-0x0000000004F70000-memory.dmp