SecurityOnlineDo Son
BlackNevas ransomware destroys virtual machines through vCenter
Part of the BlackNevas story · since 13 Nov
- Fri 13 Nov, 10:00 UTC. Securelist, first report. BlackNevas Ransomware Destroys VMware Virtualisation Estate.
- Tue 17 Nov, 10:01 UTC. SecurityOnline, its first report on the story. BlackNevas ransomware destroys virtual machines through vCenter. This article, 2nd of 2.
Kaspersky Global Emergency Response Team (GERT) traced a 10-day intrusion in which BlackNevas ESXi ransomware destroyed an organisation’s virtual infrastructure without exploiting any hypervisor vulnerability. The attackers harvested credentials from the backup systems and planted two persistence tools on a vCenter Server Appliance. They then used vCenter Host Profiles to switch on SSH across four ESXi hosts, preparing for the final wipe.
Before detonating the ransomware binary, they encrypted the backup servers and locked out administrators. The incident report emphasises that no guest-to-host escapes or hypervisor memory corruption occurred; all actions against ESXi were executed via legitimate VMware management interfaces.
Infection and impact details point to a carefully staged sequence. On the disaster-recovery vCenter appliance, the intruders logged in as root over SSH, installed MeshAgent, and later registered a Ligolo-ng reverse tunnel as a systemd service, blending in with routine appliance tasks. The attackers used a modified Host Profile to enable TSM-SSH, pushed the profile from vCenter to the managed hosts, and then moved to the destructive phase.
The ransomware payload targeted the /vmfs/ volume, overwrote the first 2 kilobytes of virtual disk files, and caused all running guest VMs to become unbootable within about three hours. The incident, observed in late 2024, has been attributed to BlackNevas in the ransom notes, with some links to the Trigona ransomware lineage noted by researchers, though the exact family implementation is rated medium-to-high confidence due to missing binary evidence.
Defense guidance from Kaspersky and Gridinsoft stresses isolating vCenter as a Tier 0 asset, monitoring for Host Profile remediations that enable SSH outside maintenance windows, and securing backup infrastructure on separate identities.
How the story developed
2 articles from 2 outlets since 13 Nov. Picked up again today after 4 days quiet. This was the 2nd report, 4 days after the first.
- Fri 13 Nov, 10:00 UTC. Securelist, first report. BlackNevas Ransomware Destroys VMware Virtualisation Estate.
- Tue 17 Nov, 10:01 UTC. SecurityOnline, its first report on the story. BlackNevas ransomware destroys virtual machines through vCenter. This article, 2nd of 2.
- No CVE
- Larger: an outlet’s first report
- Coverage over time
- Quiet time, folded
Show all 2 articles as a listHide the list
- Fri 13 NovDay 01
- BlackNevas Ransomware Destroys VMware Virtualisation Estate10:00 · Securelist · First report
Quiet for 4 days
Tue 17 NovDay 41- BlackNevas ransomware destroys virtual machines through vCenter10:01 · SecurityOnline · Picked up again · This article, 2nd of 2