Hackers executed a supply‑chain attack that hijacked a chunk of Internet address space used for updating cloud‑management software, delivering malware to networks during two intervals that together spanned a 33‑hour window.
Key Takeaways
- Attackers leveraged a BGP hijack to seize IP blocks assigned to Softaculous.
- Weak routing‑security settings at Hetzner Online and lax TLS‑certificate issuance enabled the takeover.
- The hijack unfolded in two separate bursts within a total of 33 hours, after which Hetzner reclaimed the address space.
| Metric | Value | Why it matters |
|---|---|---|
| Attack type | Supply‑chain BGP hijack | Allows malicious redirection of legitimate traffic. |
| Targeted software | Softaculous update channel | Users receive what appears to be authentic updates. |
| Hosting provider | Hetzner Online | Routing‑security gaps gave attackers a foothold. |
| Duration | Two intervals within 33 hours | Shows the attack was sustained and coordinated. |
What the hijack actually did
By commandeering the IP prefixes that Softaculous uses to distribute cloud‑management updates, the attackers were able to inject malicious binaries into the update stream. Because the traffic appeared to originate from legitimate Softaculous servers, victim systems automatically trusted and installed the payload.
How the BGP hijack was enabled
The threat actors first identified a weakness in Hetzner Online’s routing‑security configuration. By exploiting that gap, they announced ownership of the Softaculous address block via BGP, a protocol that governs how autonomous systems exchange routing information on the Internet. Simultaneously, they manipulated the process for obtaining valid TLS certificates, further masking the malicious traffic as encrypted and trustworthy.
Why Softaculous was an attractive vector
Softaculous, a UAE‑based platform that automates the installation and management of web applications, also develops Virtualizor, a virtualization management suite. Its update mechanism is widely used across shared‑hosting environments, meaning a successful compromise could cascade to thousands of downstream servers with minimal user interaction.
Routing‑security lapses at Hetzner Online
Hetzner Online’s lax routing‑security posture—specifically, insufficient filters on BGP announcements—allowed the hijack to go undetected long enough for the attackers to push malicious updates. The incident underscores the importance of route‑origin validation (RPKI) and strict BGP session controls for any provider handling critical address space.
Timeline of the two‑interval hijack
The intrusion unfolded in two distinct periods. During the first interval, Hetzner Online eventually reclaimed the hijacked address block, cutting off the attackers’ traffic flow. A second interval followed later within the same 33‑hour window, indicating that the threat actors either re‑established the BGP announcement or exploited a separate vulnerability before the network was fully restored.
Why it matters
This incident demonstrates how a single routing misconfiguration can cascade into a full‑blown supply‑chain compromise, affecting not just the targeted software vendor but any downstream customer that trusts automatic updates. Organizations that rely on third‑party update channels must now scrutinize the integrity of the underlying routing paths and TLS certificate issuance processes, in addition to traditional endpoint security controls.
Frequently asked questions
Who carried out the attack?
The perpetrators remain unidentified; the source refers to them only as “unknown attackers.”
What software was compromised?
The hijack targeted the update infrastructure of Softaculous, the UAE‑based web‑application installer and manager.
Which hosting provider’s network was abused?
Hetzner Online’s routing‑security configuration was exploited to announce ownership of the Softaculous IP block.
How long did the hijack last?
The malicious BGP announcements persisted across two intervals that together covered a 33‑hour period.
What can operators do to prevent similar attacks?
Implementing strict BGP filtering, adopting RPKI for route validation, and enforcing robust TLS‑certificate issuance policies are essential steps to mitigate hijack risks.
Bottom Line
A supply‑chain attack leveraged a BGP hijack of Softaculous’s update IP space, exploiting weak routing security at Hetzner Online and lax TLS certificate controls to deliver malware to unsuspecting users over a 33‑hour window. The episode highlights the critical need for hardened BGP practices and vigilant certificate management in any ecosystem that relies on automated software distribution.
Reporting based on: original source.
Comments
Post a Comment