By Hamza Faisal
Developer hosting platform Zeabur is shutting down after a second security breach in two months exposed millions of sensitive records, including the environment variables developers use to store database passwords, API keys and other secrets. The company said it will begin winding down services on December 1, with all dedicated servers and shared clusters going offline by December 31, 2026.
Zeabur, a Taiwan-founded platform popular with developers who build and deploy with AI-assisted tools, disclosed the intrusion in a preliminary incident report on October 19. The attacker struck on October 14 and 15, using leaked internal credentials to break into the company's shared cluster, some dedicated servers and its internal systems, and eventually read the platform database.
The haul was large. Zeabur confirmed the attacker read 3,218,965 environment-variable records and data belonging to 321,810 accounts. The exposed account data includes email addresses, usernames, phone numbers and project, environment and service details, alongside the secrets themselves.
Root access to 101 customer servers
The intrusion went further than the database. The attacker gained root access to 101 customer servers on Google Cloud that Zeabur manages, planted their own SSH key on 50 of them, and attached copies of customer disks to virtual machines under their control. Zeabur said those disk copies have since been deleted, and that it has revoked the compromised secrets.
According to the company's preliminary report, the attacker used internal AWS keys and Kubernetes cluster admin tokens that had been sitting in plaintext in a private configuration repository, with nothing forcing those tokens to expire. The cluster's admin endpoint was reachable from the internet, giving the attacker a direct route in once the credentials were in hand.
A second breach in two months
The October intrusion was Zeabur's second breach in about two months, and that history is central to why the company is closing. In August, an attacker exploited a customer-deployed NextChat application hosted on the platform, gained access to the shared cluster and eventually reached the production environment. Zeabur said at the time that it had blocked the intrusion path, rotated internal credentials and rolled out security upgrades.
The October attack suggests that work was incomplete. Reporting on the incident points to credentials obtained during the August incident still being usable, with the company acknowledging it had failed to complete a full credential rotation and harden its services after the first breach. In its shutdown notice, Zeabur said the two incidents had made the shortcomings in its security and operations even clearer.
What users should do now
For customers, the shutdown adds a hard deadline to an already urgent cleanup. Zeabur has urged users to rotate any secrets that may have been exposed, and security advisers say affected hosts should be rebuilt rather than simply patched, since the attacker held root access and planted their own keys. Applications must also be migrated off the platform before the December deadlines.
The checklist is short but unforgiving. Revoke and replace every credential that passed through Zeabur, including API keys, database passwords and cloud tokens, and check connected services for unexplained usage or charges. Rebuild any server the attacker may have touched. Move applications to a new provider well before December 1.
Zeabur's closure is a warning for the wider vibe-coding boom, where small teams ship quickly on hosted platforms. When the platform holding those secrets is breached twice in two months, the blast radius is every service those secrets unlock. The December 31 deadline is final, and any credential left unrotated will outlive the company that lost it.



