General
- Target Madium.exe
- Size 2.8MB
- Sample260620-eyjwvaet6z
- SHA256 1b5b4a0561f9844f59e0b52069a5c3eb5977208a29cd25bddccff8ef8391dae5
- MD5 265e831f3f4a7f9e9f0bd340ccd48970
- SHA1 29c5c9b33faba17463103e651d2372c8bd53b181
- SHA512 9613528bff38710e53dc23a0cf11de3974a50da06b9034dcaa8dd9608c5596aeec366516ae037528f757bddbdcbc110563e9fb0eeb368a829033b07de4287c03
- SSDEEP 49152:RgVUlsHjkmiGWU5FLGpMZ7iKPJ5W1tsclR0BxMzaRw4D6WZ:RgVUuHjkDGjzqpgmwQ1GuRxzew
- TLSH T131D5121C33FACB18F2AF4BB4A87189664371FD179C62D76C58A5399E04B6F48BA10713
- MD5 SHA1 SHA512 SSDEEP TLSH
Behavioral task
behavioral1
Sample
Madium.exe
Resource
win10v2004-20260513-en
14 signatures
150 seconds
Behavioral task
behavioral2
Sample
Madium.exe
Resource
win11ltsc2024-20260618-en
14 signatures
150 seconds
Malware Config
Extracted
Family
-
ratonrat
Version
-
Professional
C2
-
portbuddy.dev:42757
Mutex
-
PXeV2TxTknUQPXOfculP9c3
Attributes
-
assist
true
-
box
true
-
box_icon
Error
-
box_msg
AN ERROR HAPPENED TRY OPENING AS ADMIN
-
box_title
ERROR:404
-
defender
true
-
delay
0
-
hide_file
true
-
open_website
false
-
process_critical
true
-
raw
silly21
-
reconnect
3
-
startup
true
-
tag
Infected
-
uac
true
-
vm
true
-
website
https://t.me/example
Targets
-
- Target Madium.exe
- Size 2.8MB
- SHA256 1b5b4a0561f9844f59e0b52069a5c3eb5977208a29cd25bddccff8ef8391dae5
- MD5 265e831f3f4a7f9e9f0bd340ccd48970
- SHA1 29c5c9b33faba17463103e651d2372c8bd53b181
- SHA512 9613528bff38710e53dc23a0cf11de3974a50da06b9034dcaa8dd9608c5596aeec366516ae037528f757bddbdcbc110563e9fb0eeb368a829033b07de4287c03
- SSDEEP 49152:RgVUlsHjkmiGWU5FLGpMZ7iKPJ5W1tsclR0BxMzaRw4D6WZ:RgVUuHjkDGjzqpgmwQ1GuRxzew
- TLSH T131D5121C33FACB18F2AF4BB4A87189664371FD179C62D76C58A5399E04B6F48BA10713
- MD5 SHA1 SHA512 SSDEEP TLSH
-
Detects RatonRAT payload
-
Looks for VirtualBox Guest Additions in registry
-
Command and Scripting Interpreter: PowerShell
Run Powershell to modify Windows Defender settings to add exclusions for file extensions, paths, and processes.
-
Looks for VMWare Tools registry key
-
Checks BIOS information in registry
BIOS information is often read in order to detect sandboxing environments.
-
Executes dropped EXE
-
Maps connected drives based on registry
Disk information is often read in order to detect sandboxing environments.