ByteToBreach's ByteToCrypt Ransomware Threatens ESXi Data Without Hypervisor-Specific Features
Malware Intelligence · 2 sources · Updated 1mo ago · First seen Jul 24, 2026

TLPBLACK analyzed ByteToCrypt, a custom Linux ransomware strain used by ByteToBreach, which was linked to the July 2026 attack on Romania’s ANCPI that caused a prolonged outage of public-facing services. Although deployed in VMware ESXi environments, ByteToCrypt is a generic encryptor that targets files beneath its current working directory rather than using hypervisor-specific capabilities. It encrypts files with per-file AES-256-CBC keys wrapped by an embedded RSA-4096 public key, then executes anti-forensics commands. Researchers found no practical cryptographic weakness enabling decryption without the necessary keys. However, unreliable error handling can leave surviving plaintext, truncated ciphertext, orphaned temporary files, or unrecoverable data loss while reporting success.
ByteToCrypt adds to the infrastructure-level ransomware risk documented by VMware across families including Babuk, BlackCat/ALPHV, LockBit, and RansomEXX. Many ESXi-targeting strains encrypt virtual-machine files and stop VMs before encryption, allowing attacks on shared virtualization infrastructure to disrupt entire data centers; ByteToCrypt should not be assumed to have those same capabilities. Defenders should prioritize protected backups, restricted access to virtualization management systems, and recovery testing. For ByteToCrypt incidents, recovery depends on obtaining the matching RSA private key, capturing live per-file encryption keys, or restoring original data from backups, surviving plaintext, or storage artifacts—not on a demonstrated cryptographic bypass.


