BlackNevas Ransomware Wipes VMware ESXi Infrastructure and Backups Without Exploiting Any Flaws

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


A ransomware attack linked to BlackNevas destroyed an organization’s VMware environment during a 10-day intrusion, targeting four ESXi hosts, every hosted virtual machine, two vCenter Server Appliances, and connected backup infrastructure.

The attackers used legitimate management interfaces rather than exploiting virtualization vulnerabilities, showing how stolen administrative access can undermine hypervisor security.

The distinction matters: investigators found no guest-to-host escape or hypervisor memory corruption. Credentials stolen from systems outside the virtualization environment opened access to vCenter.

Earlier reporting on BlackNevas ransomware encryption tactics documented the group’s operations, but this investigation shows how management access enabled broader destruction.

Researchers Elsayed Elrefaei and Mohamed Ghobashy, writing for Securelist’s ESXi ransomware investigation, identified BlackNevas in the ransom notes.

Their November 13 report explains that the ESXi payload was unavailable for analysis, limiting binary-level attribution and verification of some command-line options.

BlackNevas Ransomware Wipes VMware ESXi Infrastructure and Backups

The attackers extracted stored credentials after gaining administrative execution on backup infrastructure. Those systems became a bridge into other infrastructure, illustrating why backup servers require protection beyond their role as recovery tools.

Valid-account access also made malicious activity harder to distinguish from normal administration. On the disaster-recovery vCenter appliance, the intruders authenticated as root through SSH and deployed MeshAgent just 43 seconds later.

The initial session lasted two minutes and 26 seconds. Roughly four hours afterward, they returned through MeshAgent and installed a persistent Ligolo-ng reverse tunnel using a VMware-looking systemd service.

Next, the attackers abused vCenter Host Profiles, a legitimate feature for enforcing host configurations. They changed the TSM-SSH service state to enable direct SSH access on ESXi hosts.

The virtualization trust stack and recurring entry paths (Source - Securelist)
The virtualization trust stack and recurring entry paths (Source – Securelist)

From the first configuration read to SSH becoming available, the sequence took approximately eleven minutes. Subsequent connections originated from vCenter itself, a normally trusted management source.

This exposed a major monitoring gap. Security agents inside virtual machines cannot directly observe the hypervisor process modifying their virtual disks.

Separate research into GhostFrame ESXi credential theft highlights the same visibility problem, although investigators did not connect that toolkit to this incident.

The payload arrived through SFTP, and authentication logs recorded a FlowSsh client identifier. A self-test ran for approximately 16 seconds around three hours before destructive execution, creating a potential detection window.

On the disaster-recovery host, all virtual machines stopped within 23 seconds; investigators could not establish the exact shutdown technique.

The final execution targeted VMFS storage with wiping and directory-traversal options. Artifacts indicated that roughly the first 2 KB of virtual-disk files had been overwritten.

That damage can prevent booting, but it does not prove every disk is unrecoverable: surviving backup partition metadata and the extent of other damage determine recovery prospects.

Backup Destruction, Detection, and Recovery Lessons

The attackers weakened recovery before disrupting production. Antivirus protection in the backup environment was disabled days earlier.

They later stopped backup services, encrypted recovery infrastructure, and disrupted administrative access before triggering the ESXi payload. This sequence left defenders without their expected restoration path when virtual machines failed.

Compromise of the management plane converted a legitimate compliance mechanism into an access path to the managed hypervisor (Source - Securelist)
Compromise of the management plane converted a legitimate compliance mechanism into an access path to the managed hypervisor (Source – Securelist)

Previous cases involving ransomware targeting Veeam backups demonstrate the wider interest in recovery systems. However, those incidents involved vulnerability exploitation; Securelist did not observe the Veeam flaws discussed in its report being exploited here.

Shared credentials and connected management systems were central concerns in this case. Defenders should correlate unexpected Host Profile changes with SSH enablement, new connections from vCenter, executable staging, and mass VM shutdowns.

Authentication, shell, host-management, and vCenter task logs provide essential evidence. Forwarding those logs outside the affected environment reduces the chance that attackers or a reboot erase the investigation trail.

Securelist recommends separate administrative identities for production, virtualization, and backups, alongside restricted management access and tested recovery procedures.

Immutable storage alone is insufficient when attackers can compromise the accounts, servers, or network paths needed to restore it.

Indicators of compromise (IoCs):-

Type Indicator Source context
Service vmware-vdma VCSA persistence
Service vspbind Windows remote-management agent
Domain api.cloudvflare[.]com Ligolo-ng command server
IPv4 45.149.154[.]135 Remote-management command server
IPv4 91.92.242[.]121 Initial portal access
IPv4 31.41.33[.]212 Initial portal access
IPv4 188.240.57[.]94 Initial portal access
SHA-1 28f8da19ddcdf26e426875c7a834b34a79bc1c33 svhost.exe / lock.exe
SHA-256 15dc419b7fbeb50c50820a7cd27997541deafa4fa710f074bb657f0149574baf Remote-management agent
SHA-256 5a9b7a0d3f25757aea957713d7e84cabec87597b3474368328a8fd5ed7a12f78 Installed agent variant

Note: IP addresses and domains are intentionally Qdefanged (e.g., [.]) to prevent accidental resolution or hyperlinking. Re-fang only within controlled threat intelligence platforms such as MISP, VirusTotal, or your SIEM.

Give your SOC the alert context on the latest threats to stop incidents quickly -> Integrate Threat Intel from 16K SOCs

The post BlackNevas Ransomware Wipes VMware ESXi Infrastructure and Backups Without Exploiting Any Flaws appeared first on Cyber Security News.