Zeabur Ends Run After Repeated Security Failures

Why Did Zeabur Fail to Protect User Data

Development platform Zeabur announced the closure of its services following a second major security breach within two months. The company confirmed that attackers exploited leaked internal credentials stored in plaintext. This vulnerability allowed unauthorized access to its core infrastructure. The incident resulted in the theft of over 3.2 million environment variable records. Data belonging to 321,810 user accounts was also compromised.

The attackers leveraged stolen administrator credentials and cloud access keys to escalate their privileges. They moved laterally across the system to extract sensitive configuration data. Zeabur stated that the breach exposed critical operational secrets. The platform had previously suffered a similar attack just weeks earlier. This pattern of failures eroded user trust significantly.

Zeabur admitted that storing internal credentials in plaintext was a critical design flaw. The company acknowledged that this practice made the breach inevitable. Attackers gained full administrative control of the cloud environment. They exfiltrated environment variables containing API keys and database passwords. The volume of stolen data was massive. Over 3.2 million records were taken. This included sensitive configuration files for all active projects.

What Happens to Your Data Now

User accounts were also targeted. 321,810 accounts had their personal and project data exposed. Zeabur emphasized that no customer source code was stolen. However, the exposure of environment variables posed a severe risk. These variables often contain secrets needed to access other third-party services. The company noted that the breach highlighted systemic weaknesses in its security architecture.

Zeabur will cease operations to manage the fallout from the breach. Existing projects will be archived and made available for download. Users are advised to rotate all API keys and passwords immediately. The company will provide a detailed incident report. This report will outline the timeline and remediation steps taken.

Customers should audit their integrations for any exposed secrets. The shutdown allows Zeabur to focus on securing the remaining data. It also prevents further exploitation of the compromised infrastructure. The decision reflects a strategic pivot toward stability over growth.

Frequently Asked Questions

Will my project data be safe after the shutdown? Zeabur will archive all project data and offer download links. Users should retrieve their code and configurations before the service goes offline.

How many accounts were affected by the breach? A total of 321,810 accounts were compromised in the incident. The breach also stole over 3.2 million environment variable records.

Should I change my passwords now? Yes. You should rotate all API keys and passwords immediately. This prevents attackers from using stolen credentials to access your other services.