BGP Hijack Delivers Malicious Virtualizor Update That Establishes Persistent Root Access
A BGP hijacking attack allowed attackers to deliver a malicious Virtualizor update package to several servers, resulting in root-level compromise on some systems. The attackers injected code into Virtualizor files, installed a Java payload, and established persistence through a systemd service. The incident highlights a critical vulnerability in Virtualizor's update process and emphasizes the importance of rigorous package verification and API key management. The vendor has released Patch 9 with a Security Analyzer, but package signing remains a future work item.
A BGP hijacking attack delivered a malicious Virtualizor update package to several servers, leading to root-level compromise on some systems. Hackers initially diverted Softaculous traffic through a BGP hijack, gaining access to a valid Let's Encrypt certificate. This allowed them to bypass update verification and install a modified Virtualizor package. The AlbaHost account reported that five of its 34 Virtualizor hypervisor nodes contained the same malicious modifications, including an injected string and a new account named 'proxyuser'.
The attackers injected code into legitimate Virtualizor files, installing Java 17 when it wasn't present, and downloading a Java payload. The payload established persistence through a systemd service and created an unauthorized account. A successful SSH login from 193.32.127[.]248 further confirmed the compromise. The incident revealed that Virtualizor had not yet implemented package signing and lacked a definitive list of affected installations.
Virtualizor released Patch 9 with a Security Analyzer on September 1st. The vendor advises operators to check for /etc/systemd/system/java-jre-update.service, rotate API keys, restrict API access, audit SSH keys, run the official scanner (SHA-256: 73e74402b3a61c7bab289fc11347bd54c7fcdc2fa2e410f4c3de9d6cd7377d48 as of September 2, 2026), and contact support before remediating a compromised host. The scanner checks for various indicators of compromise, including injected strings, a systemd unit, installed payloads, marker files, core files, and a command-and-control domain.
As of September 2, Virtualizor had not published a malicious package filename or hash, an affected update-channel list, or a build that enforces package signing. The incident advisory names the release Virtualizor 3.2.9.9, while the release note calls it Virtualizor 3.2.9 (Release Candidate and Stable Branch) (Patch 9).