Malware · 3 min read
Kaspersky: BlackNevas wiped ESXi hosts through vCenter, not a hypervisor bug
A November 13 Securelist report describes a 10-day intrusion that destroyed four ESXi hosts, both vCenter appliances and the backups. Every step used legitimate VMware management.

Kaspersky’s emergency response team has published a second look at ransomware that never needed to break the hypervisor. On November 13, 2026, Securelist described an intrusion in which BlackNevas destroyed an organization’s virtual machines by using vCenter the way an administrator would. This is not the monitoring-password case we covered on November 9. The victim, the path and the scale are different. The lesson is the same: a login to the management plane is enough.
What the investigation found
The report says the attacker spent about 10 days in the environment, then destroyed four ESXi hosts, every virtual machine on them, both vCenter appliances, and the connected backups. Ransom notes named BlackNevas, a group Kaspersky says was first seen in November 2024. No guest-to-host escape and no memory bug in the hypervisor were used. Every action against ESXi went through VMware’s own management interfaces.
Kaspersky says the organizations in this line of cases run unsupported ESXi versions, which makes the estate easier to attack, and that the ESXi locker follows from the Babuk source that leaked in September 2021. At least ten later families have reused that code. The report does not name the victim or say when the 10 days began.
The point Kaspersky stresses for defenders is visibility. Security tools inside a virtual machine do not see a process on the host that is encrypting that machine’s disk. The useful logs are on the management plane, and they have to be stored somewhere the attacker cannot wipe along with the hosts.
What you can do
- Treat vCenter as the system that can take the rest of the network down. Separate the accounts that run it from ordinary administrator accounts, and require a second factor.
- Keep ESXi Shell and SSH off unless a specific job needs them, and turn them off again when the job is done.
- Do not keep backups where the same login that administers vCenter can delete them. Kaspersky’s case lost the backups with the hosts.
- If you are on an unsupported ESXi release, plan the upgrade. Kaspersky says those versions are the ones it is seeing hit. An unsupported host is still your production if the virtual machines are.
- If you only use an app that happens to run in a virtual machine, you do not reconfigure vCenter. Ask the operator whether management logins and backups are separate.
How Frame helps
Frame can also look up your verified emails in Have I Been Pwned’s breach database. This incident is about virtualization management, not a list of personal addresses. Frame doesn’t scan hypervisors.
Related coverage
- Kaspersky: reused root passwords and monitoring access let ransomware hit ESXi and Proxmox: the earlier cases, including a different BlackNevas path through a monitoring tool.
Sources
- Kaspersky Securelist, Ransomware at the hypervisor layer: how attackers use ESXi and vCenter features for malicious purposes, November 13, 2026
More stories
New posts, by email.
About once a month. Plain-language privacy notes, nothing else. I never share your address.


