Press TechRound interviews Secure.com CEO on the future of AI security
Read

Hackers Turn a VMware vCenter Fix Into a Global Break-In

A critical VMware vCenter vulnerability is under active attack worldwide, hitting 361 servers across 47 countries just days after disclosure.

Dateline: August 18, 2026

VMware vCenter Under Siege: What CVE-2026-59310 Really Cost

Five days. That is all it took for attackers to weaponize a freshly disclosed flaw in VMware vCenter and walk into 361 servers across 47 countries. The patch was meant to shut the door. Instead it handed intruders a map.

What Happened?

On July 29, 2026, Broadcom disclosed CVE-2026-59310, a path traversal bug in the vCenter Server syslog service. It scores 9.8 out of 10, near the top of the severity scale. Here is why it stings: no login required. An attacker with network access can write files anywhere on the appliance, then plant a scheduled job that runs as root. From there, they own the box.

By August 3, the first victim appeared. By August 5, 95% of the eventual 361 targets were already compromised. Germany, the United States, Turkey, Iran, and France absorbed the heaviest load, roughly 185 servers between them. Researchers tracking the wave tied it, with moderate confidence, to a state aligned group working out of a UTC+8 time zone, based on language artifacts and tooling patterns.

What’s the Impact?

vCenter is the control room for a VMware estate. Whoever holds it holds the keys to every virtual machine underneath. In this campaign that access got used hard.

Attackers dropped the open source reverse_ssh tool for a quiet way back in, created admin accounts with names like vcadmin and vcenter_admin, and reached down into ESXi hosts and datastores. Some intrusions ended in ransomware, a Babuk variant that renames files with a .babyk extension. In plain terms: encrypted VMs, a backdoored hypervisor, and a cleanup measured in weeks.

The timing is the real lesson. A public advisory is a starting gun for both sides. Defenders who wait a week to patch are racing an opponent who started reading the same advisory on day one.

How to Avoid This

Patch first. Move vCenter to 9.1.0.0300, 9.0.2.0100, or the 8.0 U3k / U2f branch, whichever matches your build. Then assume the window between disclosure and your patch may already have been used against you:

  • Pull vCenter and ESXi management interfaces off the open internet. They belong on a restricted network, never a public IP.
  • Hunt for rogue cron jobs in /etc/cron.d and unfamiliar service accounts on the appliance.
  • Watch for outbound SSH from vCenter. A control plane server dialing out is a red flag.
  • Check the IOC list and preserve logs before you rebuild anything.

Indicators of Compromise

CVE-2026-59310 · VMware vCenter Syslog path traversal

CVSS 9.8 Critical Disclosed Jul 29, 2026 Exploited from Aug 3, 2026 Victims 361 IPs / 47 countries

IP addresses & ports

Callback / C25.34.177.38:9861
Callback / C25.34.177.38:9564
Callback / C2185.144.28.120:3232
Callback / C2192.255.141.13:8080
Callback / C2192.255.141.13:7788
Callback / C25.34.176.100:5244
Source / infra146.59.252.178
Source / infra146.56.116.119
Source / infra78.135.91.204
Source / infra141.95.158.73

Domains & URLs

C2 endpointintel.se9ly9upbhay.shop:8080/ws
Staging hostprofound-beijinho-504b1f.netlify.app
Payload hosttmpfiles.org

File hashes

SHA-1 ransomwaree876ceb47ba092420a97724a957152b3808568b0

Files & paths

Malicious cron/etc/cron.d/zz-poc59310-syslog.log
Malicious cron/etc/cron.d/zz-poc59310
Dropper/tmp/linuxFile
Payload/tmp/.x/systemlog
Payload copy/root/.local/share/cg4nQW9TOxeq/linuxFile
Web shell…/statsreport/vmware-perf-update.jsp
Script/tmp/.vmware-perf-upd.sh
Cred dump/tmp/.ldappw
Recon/tmp/.sso_domain
Persistence/var/run/backup
Rogue servicesys-9436d8.service

Created accounts

vCenter adminvcenter_admin
Adminadminuser
Adminvcadmin
Servicesvc_dAi7dDGBKk

Tooling, agents & ransomware

Persistence toolreverse_ssh
File toolAList
User-AgentGoodMoodle-VCProbe/1.0
User-AgentGoodMoodle-VCFleet/1.0
RansomwareBabuk variant · .babyk

Compiled from the researcher incident reports and corroborating public reporting on CVE-2026-59310. Treat callback IPs and hashes as high confidence; source IPs may rotate. Validate against your own telemetry before blocking. Preserve logs before remediation.