Back to all lessons
Awareness Lessons
2 months ago

BGP Hijack Delivers Malicious Virtualizor Update via Compromised Update Infrastructure

Written by AI from the linked story. Not reviewed by an editor. How this works

Threat actors exploited BGP routing vulnerabilities to intercept and redirect traffic destined for Softaculous's update servers, allowing them to serve a trojanized version of Virtualizor to unsuspecting administrators who trusted the update process. The attack highlights a critical weakness in software supply chains: update mechanisms that lack cryptographic package signing can be weaponized once an attacker gains control of routing infrastructure. BGP hijacking is particularly dangerous because it operates at the internet routing layer, making it invisible to most endpoint and perimeter defenses. This incident underscores that trusting network-layer integrity alone — without cryptographic verification of software authenticity — leaves organizations exposed to man-in-the-middle attacks at scale.

Tactical Insight

Immediate actions

  • Verify the integrity of any Virtualizor installations active between August 28–30 using the security tool released in the latest Softaculous update.
  • Audit all recently applied software updates across your environment for signs of tampering or unexpected behavior.
  • Enable BGP route origin validation (ROV) and RPKI on your network infrastructure to reject illegitimate route announcements.

Long-term improvements

  • Require cryptographic package signing and signature verification for all software update pipelines before applying any update.
  • Implement software supply chain controls such as verifying update server TLS certificates and pinning expected IP ranges for critical vendors.
  • Establish vendor communication channels (e.g., signed advisories, out-of-band notifications) to validate update authenticity during anomalous conditions.

Detection measures

  • Deploy BGP monitoring tools (e.g., BGPmon, Kentik) to alert on unexpected route changes involving your AS or trusted vendor prefixes.
  • Log and alert on unexpected changes to update server destinations or TLS certificate mismatches during software update processes.
  • Monitor host-based integrity tools for unauthorized file modifications following any software update activity.

Back this up with a control

All controls and vendors

Training helps people spot this. These controls make the attack fail even on the day someone does not.