BlackNevas Destroys VMware Environment Without Exploits

BlackNevas Ransomware Wipes VMware Estate Using Stolen Credentials

CRITICAL
November 14, 2026
5m read
RansomwareCyberattackThreat Actor

Related Entities

Threat Actors

BlackNevas

Organizations

Products & Tech

VMware ESXiVMware vCenter Server

Other

MeshAgentLigolo-ng

Full Report

Executive Summary

A recent investigation by Kaspersky's Global Emergency Response Team (GERT) has detailed a highly destructive attack by the BlackNevas ransomware group. The attackers systematically dismantled and wiped an organization's entire VMware virtualization estate, including ESXi hosts, vCenter servers, and backups. Critically, this was achieved not by exploiting software vulnerabilities, but by using legitimate administrative credentials and toolsβ€”a tactic known as Living off the Land (LotL). The attackers used stolen credentials to access vCenter, enabled SSH on the hosts using standard features, and deployed their encryptor. This incident is a stark warning that even without zero-days, a determined attacker with valid credentials can cause catastrophic damage.


Threat Overview

The BlackNevas ransomware group orchestrated a methodical, 10-day campaign to ensure the complete and irreversible destruction of the victim's virtual infrastructure. The attack was characterized by its deliberate pace and focus on eliminating recovery options before the final destructive act.

The initial intrusion vector was the use of valid account credentials, which were stolen from systems outside the virtualization environment. With these credentials, the attackers gained access to the vCenter Server Appliances. From there, they abused legitimate administrative functionality to further their attack, making their activity difficult to distinguish from normal administrative tasks. A key part of their strategy was to neutralize the backup environment first, days before the main attack, to prevent any possibility of restoration.

Technical Analysis

The attack chain highlights a masterful use of legitimate tools for malicious purposes:

  1. Initial Access: The attackers used T1078 - Valid Accounts to log into the vCenter appliances with stolen credentials.
  2. Defense Evasion & Lateral Movement Preparation: Instead of using an exploit, the attackers abused the vCenter Host Profiles feature. This legitimate tool, designed for standardized host configuration, was used to enable the SSH service across all targeted ESXi hosts. This action aligns with T1562.001 - Impair Defenses: Disable or Modify Tools by changing the security configuration to allow remote access.
  3. Lateral Movement: With SSH enabled, the attackers used SFTP (T1021.004 - Remote Services: SSH) to transfer their ESXi encryptor payload to the hosts.
  4. Impact: The attackers executed the encryptor payload, leading to T1485 - Data Destruction and T1486 - Data Encrypted for Impact. This wiped four ESXi hosts, all associated VMs, the vCenter servers, and the previously compromised backup systems.

Forensic evidence showed that the attackers ran a self-test of their encryptor hours before the final execution, indicating a careful and planned operation. They also used tools like MeshAgent and Ligolo-ng for command and control and network tunneling.

Impact Assessment

The impact of this attack was catastrophic, resulting in the complete loss of the organization's production environment and its recovery capabilities. By targeting and eliminating the backup infrastructure first, the BlackNevas group ensured that restoration would be nearly impossible, maximizing pressure on the victim to pay the ransom. This strategy demonstrates a high level of sophistication and a deep understanding of enterprise disaster recovery processes. The financial and operational costs of rebuilding an entire virtual estate from scratch are immense, leading to extended downtime and severe business disruption.

IOCs β€” Directly from Articles

No specific file hashes, IP addresses, or domains were provided in the source articles.

Cyber Observables β€” Hunting Hints

Security teams should hunt for anomalous use of administrative tools in their VMware environment:

Type
Configuration Change
Value
vCenter Host Profile modification
Description
An alert on any change to Host Profiles, especially changes that enable services like SSH across multiple hosts, could be an early indicator.
Type
Service Name
Value
TSM-SSH
Description
Monitor for the enablement of the SSH service on ESXi hosts outside of planned maintenance windows.
Type
Log Source
Value
vCenter Events
Description
Look for logins from unusual IP ranges or accounts, followed by mass configuration changes or host profile edits.
Type
Network Traffic Pattern
Value
SFTP/SCP traffic to ESXi hosts
Description
File transfers to ESXi hosts, especially from non-standard administrative workstations, are highly suspicious.
Type
Process Name
Value
backup service processes
Description
Monitor for the termination or disabling of backup agent processes on backup servers.

Detection & Response

  • Behavioral Monitoring: Deploy security solutions that can baseline normal administrative behavior within vCenter and alert on deviations. A single account enabling SSH across the entire cluster is a major red flag. D3FEND's User Behavior Analysis techniques are crucial.
  • Log Auditing: Regularly audit vCenter and ESXi logs for signs of misuse. Forward these logs to a SIEM and create specific alert rules for events like 'Host profile edited,' 'SSH service started,' or 'Firewall configuration changed.'
  • Endpoint Detection on vCenter: If possible, deploy EDR agents on vCenter Server Appliances to detect the execution of unauthorized tools or scripts.

Mitigation

  • Multi-Factor Authentication (MFA): Enforce MFA on all vCenter and ESXi administrative accounts. This is the single most effective control against attacks leveraging stolen credentials and aligns with M1032 - Multi-factor Authentication.
  • Privileged Access Management (PAM): Implement PAM solutions to vault and rotate privileged credentials, reducing the risk of credential theft.
  • Immutable Backups: Ensure that at least one copy of critical backups is immutable or stored offline in an air-gapped environment. This would have thwarted the attackers' strategy of destroying backups first. This is a form of D3FEND's Decoy Object or File Restoration preparedness.
  • Disable Unused Services: Disable SSH on ESXi hosts by default and only enable it for specific, time-bound maintenance tasks. Use ESXi Lockdown Mode to restrict administrative access.

Timeline of Events

1
November 13, 2026
Kaspersky publishes its report on the BlackNevas ransomware attack.
2
November 14, 2026
This article was published

MITRE ATT&CK Mitigations

Enforcing MFA on all administrative access to vCenter would have prevented the initial access via stolen credentials.

Mapped D3FEND Techniques:

Use PAM solutions to vault, rotate, and monitor the use of privileged accounts.

Harden ESXi hosts by disabling unused services like SSH by default and using Lockdown Mode.

Mapped D3FEND Techniques:

Maintain immutable and/or air-gapped backups that cannot be destroyed by an attacker with access to the production environment.

Timeline of Events

1
November 13, 2026

Kaspersky publishes its report on the BlackNevas ransomware attack.

Sources & References

gbhackers.com
GBHackers on Security (gbhackers.com)
f4n6.co.uk
f4n6.co.uk (f4n6.co.uk)
blog.gridinsoft.com
Gridinsoft (blog.gridinsoft.com)

Article Author

Jason Gomes

Jason Gomes

β€’ Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.

Tags

RansomwareBlackNevasVMwareESXivCenterLiving off the Land

πŸ“’ Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

πŸ›‘οΈ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

πŸ”— STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph β€” relationships between actors, malware, techniques, and indicators.

⚑ Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.