Executive Summary
In late August 2026, attackers executed a sophisticated supply chain attack against Virtualizor, a popular virtualization management platform, by hijacking Border Gateway Protocol (BGP) routes to redirect software update traffic. The attack occurred between August 28-30, 2026, when threat actors diverted Softaculous traffic to attacker-controlled servers and delivered malicious Virtualizor updates that established persistent root access on affected systems. At least 5 of 34 hypervisors at one hosting provider were compromised, with attackers installing backdoors, creating unauthorized accounts, and maintaining persistence through systemd services.
This incident highlights the growing sophistication of supply chain attacks targeting critical infrastructure management software. As organizations increasingly rely on automated software updates and third-party platforms for cloud operations, attackers are exploiting trust relationships and network-level vulnerabilities to achieve widespread compromise with minimal detection.
Why This Matters Now
BGP hijacking attacks are increasingly targeting software supply chains, exploiting the implicit trust in update mechanisms. With critical infrastructure heavily dependent on virtualization platforms, even brief network diversions can lead to widespread compromise across hosting providers and cloud environments.
Attack Path Analysis
Attackers executed a BGP hijack to redirect Virtualizor update traffic to an attacker-controlled server with a valid Let's Encrypt certificate. The malicious update package was delivered to systems without cryptographic verification, injecting code into core Virtualizor files. Root-level access was established through cron job execution, enabling the installation of Java runtime and persistent backdoors. Command and control was established through systemd services and C2 domains, while unauthorized SSH access was obtained via injected keys and a proxy user account. The attack potentially exposed client authentication data and payment information during the traffic diversion window.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
BGP hijacking redirected legitimate Virtualizor update traffic to attacker-controlled infrastructure with valid TLS certificate, delivering malicious packages without cryptographic verification
MITRE ATT&CK® Techniques
Adversary-in-the-Middle: ARP Cache Poisoning
Supply Chain Compromise: Compromise Software Supply Chain
Create or Modify System Process: Systemd Service
Create Account: Local Account
Scheduled Task/Job: Cron
Abuse Elevation Control Mechanism: Sudo and Sudo Caching
Valid Accounts: Local Accounts
Application Layer Protocol: Web Protocols
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Software integrity validation
Control ID: 6.3.2
NYDFS 23 NYCRR 500 – Third Party Service Provider Security Policy
Control ID: 500.11
DORA – ICT Third Party Risk Management
Control ID: Article 11
CISA Zero Trust Maturity Model 2.0 – Data Integrity and Validation
Control ID: DA.L2
NIS2 Directive – Supply Chain Security Measures
Control ID: Article 21.2(a)
ISO 27001:2022 – Information security policy for supplier relationships
Control ID: A.15.1.1
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Information Technology/IT
Virtualizor BGP hijack compromises hosting infrastructure through malicious updates, establishing persistent root access and threatening cloud service provider operations globally.
Internet
BGP routing manipulation diverts legitimate traffic to attacker infrastructure, compromising certificate validation and update mechanisms across internet service providers.
Telecommunications
Border Gateway Protocol vulnerabilities enable traffic hijacking affecting network routing integrity, potentially compromising telecommunications infrastructure and customer data flows.
Computer Software/Engineering
Supply chain attack targets virtualization software updates without cryptographic verification, exposing software development and distribution processes to persistent compromise.
Sources
- BGP Hijack Delivers Malicious Virtualizor Update That Establishes Persistent Root Accesshttps://thehackernews.com/2026/09/bgp-hijack-delivers-malicious.htmlVerified
- Security Incident - BGP Hijacking - Virtualizor Bloghttps://www.virtualizor.com/blog/security-incident-bgp-hijacking/Verified
- Virtualizor 3.2.9 Launched - Release Candidate Patch 9https://www.virtualizor.com/blog/virtualizor-3-2-9-launched-release-candidate-patch-9/Verified
- RIPE Stat BGP Updates Datahttps://stat.ripe.net/data/bgp-updates/data.json?resource=162.55.80.0%2F24&starttime=2026-08-28T20%3A50%3A00&endtime=2026-08-30T10%3A00%3A00Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF would likely reduce the blast radius of this BGP hijack attack by constraining lateral movement between hypervisor nodes and limiting unauthorized egress communications. While the initial compromise through traffic redirection would still occur, segmentation controls could significantly contain the spread across hosting infrastructure.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Cloud native security fabric would likely provide enhanced visibility into anomalous network flows and certificate usage patterns, potentially alerting administrators to suspicious update traffic redirection during the BGP hijack window
Control: Zero Trust Segmentation
Mitigation: Zero trust segmentation would likely limit the scope of root-level access by constraining which systems and resources the compromised hypervisor nodes could reach, reducing the effective blast radius of the privilege escalation
Control: East-West Traffic Security
Mitigation: East-west traffic controls would likely constrain the spread from the initially compromised hypervisor to additional nodes, potentially reducing the number of systems affected from the observed 5 of 34 compromised hosts
Control: Multicloud Visibility & Control
Mitigation: Multicloud visibility controls would likely detect and alert on suspicious systemd service creation and anomalous outbound communications to the C2 domains, enabling faster incident response and containment
Control: Egress Security & Policy Enforcement
Mitigation: Egress security policies would likely limit unauthorized outbound data transfers from compromised hypervisor nodes, constraining the attackers' ability to exfiltrate sensitive client authentication and payment information
While persistent backdoor accounts would likely remain on compromised systems, the effective reach and operational capability of these accounts would be significantly constrained by ongoing segmentation and egress controls
Impact at a Glance
Affected Business Functions
- Virtual Server Management
- Hosting Infrastructure Operations
- Customer VPS Services
- Server Provisioning
Estimated downtime: 3 days
Estimated loss: N/A
Potential exposure of client-area login credentials and payment details for users who accessed services during the BGP hijack window from August 28-30, 2026. Root-level compromise of hosting provider servers with unauthorized SSH access and persistent backdoors established on affected hypervisor nodes.
Recommended Actions
Key Takeaways & Next Steps
- • Implement Egress Security & Policy Enforcement to detect and block unauthorized outbound connections to C2 domains like cdn.nerat.cc and connect.ne-rat.xyz
- • Deploy Zero Trust Segmentation to prevent lateral movement between hypervisor nodes and limit blast radius of supply chain compromises
- • Enable Multicloud Visibility & Control to detect anomalous traffic patterns and suspicious automation during update processes
- • Utilize Threat Detection & Anomaly Response capabilities to identify unusual SSH access patterns and unauthorized account creation
- • Establish Encrypted Traffic controls and secure update channels with cryptographic package verification to prevent malicious payload delivery



