General
- Target 02d84ab808655cbe2cb4737e9c01544345b2f91bdfc03b29c0e061bee2e883cf.zip
- Size 655KB
- Sample260706-eqbkhahw4x
- SHA256 030bb262c95ab1b18f96c8d4a6850f725778835f3f59c8f9fba28d2488b31948
- MD5 9b593e820ee4de9a28c18c6905256f09
- SHA1 38de34b508b8dbae46fe6500b03d7546640bf736
- SHA512 a479bed8384bc6e9a27351489a9a8bb1ed49b0d0289d3c60fe7e85ce4de6553a304b6c1af2f0882b96f884eed08530db7921415990d151303f15e25087ebdd92
- SSDEEP 12288:Zy41YhmxGQMtqKXfWvhb22FMcbCDUE7jmyRf0xYychNirMyOfvZRlv7xV0A4I:g41emgQ4WvE2BbCDUEhR8xY9ErUXZRP7
- TLSH T11BE42379B4FD8A84D035CCB14863E5DA33BEC38C29B07866D6B5025C0D7FAC1F64A668
- MD5 SHA1 SHA512 SSDEEP TLSH
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
02d84ab808655cbe2cb4737e9c01544345b2f91bdfc03b29c0e061bee2e883cf.exe
Resource
win11-20260513-en
22 signatures
900 seconds
Malware Config
Extracted
Family
-
blacknet
Version
-
v3.5 Public
Botnet
-
HacKed By MustyMoney
C2
-
http://ratking.ddns.net
Mutex
-
BN[telsJjiy-9983844]
Attributes
-
antivm
false
-
elevate_uac
false
-
install_name
WindowsUpdate.exe
-
splitter
|BN|
-
start_name
14247ae8e9bdf8a07859c46cc6c701e5
-
startup
false
-
usb_spread
false
Targets
-
- Target 02d84ab808655cbe2cb4737e9c01544345b2f91bdfc03b29c0e061bee2e883cf.exe
- Size 833KB
- SHA256 02d84ab808655cbe2cb4737e9c01544345b2f91bdfc03b29c0e061bee2e883cf
- MD5 9da0947781f5d7848d9401ac3596dbcc
- SHA1 75d60cfaea3107d6f21578e0e26ffa33a66a984c
- SHA512 0357647124784104c56ae3d5fda4148b48e338affb74d3da4b4e1bfc672b3693ec23f70dc75870dae29029b8cb766c088ce9042df3b9d483bbf12df0664b159c
- SSDEEP 24576:WOrsnB6DHAa/cORj+f/ufuF+/Ev1lWCFOs0gfFt0ua1Hoc0M:brsnB6Dga/cORjb/cZ/pal
- TLSH T10305BE3D1EBA2BF1F37B9B7A4974A14492FEF6A37723C41D38D440C50B1291299E1A1E
- MD5 SHA1 SHA512 SSDEEP TLSH
-
BlackNET payload
-
Contains code to disable Windows Defender
A .NET executable tasked with disabling Windows Defender capabilities such as realtime monitoring, blocking at first seen, etc.
-
Looks for VirtualBox Guest Additions in registry
-
Looks for VMWare Tools registry key
-
Checks BIOS information in registry
BIOS information is often read in order to detect sandboxing environments.
-
Maps connected drives based on registry
Disk information is often read in order to detect sandboxing environments.
-
Suspicious use of SetThreadContext