vCenter pre-auth RCE → root on every ESXi → mass encrypt
Pre-auth RCE on vCenter Server (DCERPC or vSphere Client class CVE). Deploy SSH key via vCenter to every managed ESXi, then mass-encrypt every .vmdk — the ESXiArgs / Black Basta playbook.
§ Context
Assumed environment: target vCenter is reachable from the attacker's foothold and unpatched for a 2023+ pre-auth RCE. vCenter manages dozens / hundreds of ESXi hosts.
§ Steps
- 01Drop ransom note in vSphere UIImpactT1486— Data Encrypted for Impact
- 02Push attacker SSH key to every ESXiPersistenceT1098— Account Manipulation
- 03Identify vCenter (port 443 / 9443)DiscoveryN-NMAP-INTERNAL— Internal Nmap Sweep
- 04Pre-auth RCE on vCenterInitial AccessHV-VCENTER-RCE— vCenter Server RCE
- 05Mass-encrypt VMDKs across the estateImpactHV-ESXI-RANSOM— ESXi Mass-Encrypt Ransomware
- 06Extract cached ESXi credentials / SSO tokensCredential AccessHV-NESTED-CRED— Hypervisor Credential Caches
§ References
§ Frequently asked
- What is the "vCenter pre-auth RCE → root on every ESXi → mass encrypt" attack path?
- Pre-auth RCE on vCenter Server (DCERPC or vSphere Client class CVE). Deploy SSH key via vCenter to every managed ESXi, then mass-encrypt every .vmdk — the ESXiArgs / Black Basta playbook. It chains 6 steps drawn from real-world offensive-security techniques.
- What starting position does this attack require?
- The first step is Drop ransom note in vSphere UI (T1486) — a impact primitive. Assumed environment: target vCenter is reachable from the attacker's foothold and unpatched for a 2023+ pre-auth RCE.
- What is the final impact of this kill-chain?
- The final step lands on Extract cached ESXi credentials / SSO tokens (HV-NESTED-CRED), which falls under Credential Access. From here, an operator typically pivots into post-exploitation or maintains persistence.
- How can defenders detect or prevent this attack?
- Detection and prevention vary per step. Refer to each linked MITRE ATT&CK entry under "References" — every technique on that page lists defensive controls, detection telemetry, and known threat-actor usage.
§ Related dossiers
- Shared techniques2
Vish helpdesk → Okta MFA reset → admin → ransomware (MGM-class)
Identify an Okta admin via LinkedIn. Vish the helpdesk pretending to be that admin, get MFA reset. Sign in, plant attacker MFA factor, then push policy changes that disable MFA for chosen apps before mass-deploying ransomware.
- Shared techniques2
BACnet HVAC → disrupt building operations
BACnet on UDP/47808 is unauthenticated. From a foothold in corporate IT, write to HVAC controllers — over-cool a data centre, disable smoke evacuation, mess with elevators.
- Shared techniques2
ESXiArgs — OpenSLP unauth RCE → ransomware
Internet-facing ESXi with SLP service on TCP/427 unpatched for CVE-2021-21974. Single ROP gadget chain yields root, then a small bash script encrypts every .vmdk on local datastores.
- Shared techniques2
Reachable Modbus PLC → direct register override
Modbus has no authentication. From a foothold on a reachable OT network, write to coils / holding registers directly with pymodbus.