BlackByte is a ransomware threat actor operating since at least 2021. BlackByte is associated with several versions of ransomware also labeled BlackByte Ransomware. BlackByte ransomware operations initially used a common encryption key allowing for the development of a universal decryptor, but subsequent versions such as BlackByte 2.0 Ransomware use more robust encryption mechanisms. BlackByte is notable for operations targeting critical infrastructure entities among other targets across North America.[1][2][3][4][5]
Name | Description |
---|---|
Hecamede |
Domain | ID | Name | Use | |
---|---|---|---|---|
Enterprise | T1134 | .003 | Access Token Manipulation: Make and Impersonate Token |
BlackByte constructed a valid authentication token following Microsoft Exchange exploitation to allow for follow-on privileged command execution.[4] |
Enterprise | T1087 | .002 | Account Discovery: Domain Account |
BlackByte has used tools such as AdFind to identify and enumerate domain accounts.[4] |
Enterprise | T1583 | .003 | Acquire Infrastructure: Virtual Private Server |
BlackByte staged encryption keys on virtual private servers operated by the adversary.[1] |
Enterprise | T1071 | .001 | Application Layer Protocol: Web Protocols |
BlackByte collected victim device information then transmitted this via HTTP POST to command and control infrastructure.[4] |
Enterprise | T1560 | Archive Collected Data |
BlackByte compressed data collected from victim environments prior to exfiltration.[2] |
|
Enterprise | T1547 | .001 | Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder | |
Enterprise | T1059 | .001 | Command and Scripting Interpreter: PowerShell |
BlackByte used encoded PowerShell commands during operations.[1] BlackByte has used remote PowerShell commands in victim networks.[4] |
.003 | Command and Scripting Interpreter: Windows Command Shell |
BlackByte executed ransomware using the Windows command shell.[1] |
||
Enterprise | T1136 | .002 | Create Account: Domain Account |
BlackByte created privileged domain accounts during intrusions.[5] |
Enterprise | T1543 | .003 | Create or Modify System Process: Windows Service |
BlackByte modified multiple services on victim machines to enable encryption operations.[3] BlackByte has installed tools such as AnyDesk as a service on victim machines.[4] |
Enterprise | T1486 | Data Encrypted for Impact |
BlackByte has encrypted victim files for ransom. Early versions of BlackByte ransomware used a common key for encryption, but later versions use unique keys per victim.[1][2][3][4][5] |
|
Enterprise | T1491 | .001 | Defacement: Internal Defacement |
BlackByte left ransom notes in all directories where encryption takes place.[1] |
Enterprise | T1140 | Deobfuscate/Decode Files or Information |
BlackByte has encoded commands in base64-encoded sections concatenated together in PowerShell.[1] BlackByte uses PowerShell commands to disable Windows Defender.[2] |
|
Enterprise | T1482 | Domain Trust Discovery |
BlackByte enumerated Active Directory information and trust relationships during operations.[1][4] |
|
Enterprise | T1480 | Execution Guardrails |
BlackByte stopped execution if identified language settings on victim machines was Russian or one of several language associated with former Soviet republics.[2] BlackByte has used ransomware variants requiring a key passed on the command line for the malware to execute.[5] |
|
Enterprise | T1041 | Exfiltration Over C2 Channel |
BlackByte transmitted collected victim host information via HTTP POST to command and control infrastructure.[4] |
|
Enterprise | T1567 | Exfiltration Over Web Service |
BlackByte has used services such as |
|
Enterprise | T1190 | Exploit Public-Facing Application |
BlackByte exploited vulnerabilities such as ProxyLogon and ProxyShell for initial access to victim environments.[1][2][3][4] |
|
Enterprise | T1068 | Exploitation for Privilege Escalation |
BlackByte has exploited CVE-2024-37085 in VMWare ESXi software for authentication bypass and subsequent privilege escalation.[5] |
|
Enterprise | T1562 | Impair Defenses |
BlackByte removed Kernel Notify Routines to bypass endpoint detection and response (EDR) products.[3] |
|
.001 | Disable or Modify Tools |
BlackByte disabled security tools such as Windows Defender and the Raccine anti-ransomware tool during operations.[1][2][5] |
||
.004 | Disable or Modify System Firewall |
BlackByte modified firewall rules on victim machines to enable remote system discovery.[2][3] |
||
Enterprise | T1070 | .004 | Indicator Removal: File Deletion |
BlackByte deleted ransomware executables post-encryption.[2][3][4][5] |
Enterprise | T1105 | Ingress Tool Transfer |
BlackByte has transferred tools such as Cobalt Strike to victim environments from file sharing and hosting websites.[4] |
|
Enterprise | T1490 | Inhibit System Recovery |
BlackByte resized and deleted volume shadow copy files to prevent system recovery after encryption.[2][3] |
|
Enterprise | T1570 | Lateral Tool Transfer |
BlackByte transfered tools such as Cobalt Strike and the AnyDesk remote access tool during operations using SMB shares.[2] |
|
Enterprise | T1036 | .008 | Masquerading: Masquerade File Type |
BlackByte masqueraded configuration files containing encryption keys as PNG files.[1] |
Enterprise | T1112 | Modify Registry |
BlackByte performed Registry modifications to escalate privileges and disable security tools.[2][5] |
|
Enterprise | T1046 | Network Service Discovery |
BlackByte has used tools such as NetScan to enumerate network services in victim environments.[4] |
|
Enterprise | T1135 | Network Share Discovery | ||
Enterprise | T1003 | OS Credential Dumping |
BlackByte used tools such as Cobalt Strike and Mimikatz to dump credentials from victim systems.[2][4] |
|
Enterprise | T1055 | Process Injection |
BlackByte has injected Cobalt Strike into |
|
.012 | Process Hollowing |
BlackByte used process hollowing for defense evasion purposes.[4] |
||
Enterprise | T1012 | Query Registry |
BlackByte queried registry values to determine system language settings.[2] |
|
Enterprise | T1219 | Remote Access Tools |
BlackByte has used tools such as AnyDesk in victim environments.[2][4] |
|
Enterprise | T1021 | .001 | Remote Services: Remote Desktop Protocol |
BlackByte has used RDP to access other hosts within victim networks.[4][5] |
.002 | Remote Services: SMB/Windows Admin Shares |
BlackByte used SMB file shares to distribute payloads throughout victim networks, including BlackByte ransomware variants during wormable operations.[2][4][5] |
||
Enterprise | T1018 | Remote System Discovery |
BlackByte used tools such as Arp to identify remotely-connected devices.[1][2] |
|
Enterprise | T1053 | .005 | Scheduled Task/Job: Scheduled Task |
BlackByte created scheduled tasks for payload execution.[1][2] |
Enterprise | T1505 | .003 | Server Software Component: Web Shell |
BlackByte has used ASPX web shells following exploitation of vulnerabilities in services such as Microsoft Exchange.[2][4] |
Enterprise | T1518 | .001 | Software Discovery: Security Software Discovery |
BlackByte enumerated installed security products during operations.[4] |
Enterprise | T1608 | .001 | Stage Capabilities: Upload Malware |
BlackByte has staged tools such as Cobalt Strike at public file sharing and hosting sites.[4] |
Enterprise | T1082 | System Information Discovery |
BlackByte used various system commands and tools to pull system information during operations.[1][3][4] |
|
Enterprise | T1614 | .001 | System Location Discovery: System Language Discovery |
BlackByte identified system language settings to determine follow-on execution.[2] |
Enterprise | T1016 | System Network Configuration Discovery |
BlackByte used tools such as Arp to pull system network information and identify connected devices.[1][4] |
|
Enterprise | T1569 | .002 | System Services: Service Execution |
BlackByte created malicious services for ransomware execution.[3][5] |
Enterprise | T1078 | Valid Accounts |
BlackByte has gained access to victim environments through legitimate VPN credentials.[5] |
|
.002 | Domain Accounts |
BlackByte captured credentials for or impersonated domain administration users.[4][5] |
||
Enterprise | T1047 | Windows Management Instrumentation |
BlackByte used WMI to delete Volume Shadow Copies on victim machines.[1] |