Check Point reports intrusions through internet-facing gateways that reached VMware ESXi systems, while an international operation disrupted infrastructure used by Gootloader and StealC.
A campaign exploiting Check Point security gateways has put VMware ESXi infrastructure at risk, with destructive activity reported in a limited number of intrusions. Check Point said it observed exploitation of unpatched systems and notified affected customers. The company’s researchers described activity beginning in late October and a broader wave in early November, but said the later wave showed no evidence of destruction.
The attackers targeted internet-facing Mobile Access portals. Reports describe PHP-related exploitation and a Check Point gateway flaw used to gain access, followed by PHP webshells and backdoor components. From compromised gateways, attackers moved to ESXi hosts, using SSH access through the vpxuser service account. The activity included tools intended to conceal attacker traffic.
In some cases, attackers deployed a wiper that recursively deleted files and could overwrite them first, making recovery harder. A message found in the operation rejected ransom negotiations, consistent with sabotage rather than ordinary extortion in those incidents. Check Point has not reported that all affected systems were destroyed, and the available information does not establish that the campaign was widespread.
Check Point recommends installing its November Jumbo Hotfix on all Management Servers and Security Gateways, prioritizing systems with internet-facing Mobile Access deployments. The company said fixes had been available since October 23. CISA added the exploited gateway vulnerability to its Known Exploited Vulnerabilities catalog on November 13, another reason administrators should treat this as an urgent patch rather than routine maintenance.
Patching does not remove an attacker who may already have established persistence. Teams should inspect gateway and firewall logs for unexplained gaps, look for unexpected PHP session files and processes, and review unfamiliar files in temporary directories. Check Point’s researchers also identified rogue processes and scanner activity as clues to investigate. Administrators should compare findings with vendor guidance rather than assume every suspicious-looking artifact proves compromise.
Because the reported chain reached ESXi, teams should review hypervisor authentication and service-account activity, including SSH use by vpxuser that does not match normal maintenance. Check for unexplained file changes and verify that backups are isolated and recoverable. If compromise is suspected, isolate affected systems where operationally feasible and engage incident-response support. A hotfix is necessary, but it is not a substitute for investigating access that may have occurred before installation.
Check Point linked some of the tooling to modified PhiliKit components previously associated with attacks on Ivanti products and with the China-nexus group UNC5221. The company said the evidence does not support high-confidence attribution; false-flag activity or an initial-access broker remain possible. That uncertainty is a reason to focus on observable indicators and remediation, not to treat a suspected actor connection as confirmed.
Separately, an international law-enforcement operation disrupted infrastructure associated with Gootloader, StealC and CastleRAT, according to the Justice Department material in the source report. Authorities said they dismantled servers and domains used by the malware operations. The Justice Department reported that more than 44 U.S. ransomware victims were initially infected through Gootloader and estimated losses at $28.8 million. The operation also targeted more than 100 StealC servers and identified millions of stolen login credentials.
A takedown can disrupt criminal operations, but it cannot clean infected machines or make stolen passwords safe. IT teams should review endpoint alerts and telemetry for Gootloader or StealC activity, reset credentials where theft is suspected, revoke active sessions and tokens, and require multifactor authentication where available. Developers and administrators should rotate secrets from a clean device if they may have been stored on an affected endpoint.
The source material also refers to a cloud-provider ransomware incident and a cloud-supply-chain data breach, but supplies no details about the providers, affected customers or response. Those claims cannot be assessed from the information available. For small IT teams, the immediate priorities are concrete: patch exposed gateways, investigate persistence and lateral movement, review virtualization infrastructure, and respond quickly to suspected credential theft.

