CyberKit

Intel archive / Breaches and incidents

Zeabur breached twice, reads 3.2 million customer secrets, shuts down

An attacker used leaked internal credentials to read Zeabur's platform database, including 3.2 million environment variables holding customers' API keys and passwords. The host is closing by year end.

High severity. Active. Moderate confidence. First reported 17 Oct 2026, last activity 17 Oct 2026. Briefing updated 22 Oct 2026.

AI-written summaries of public reporting, each checked against at least two sources from different publishers. Check the sources before you act. Last refreshed 2026-11-18 14:09 UTC. How this is made.

What is not settled: Zeabur's posts could not be opened during this refresh; counts and root causes come from search excerpts of its preliminary report, which BleepingComputer reports the same way. The report is preliminary. The list of affected providers and the claim of abused AI keys come from Taiwanese coverage, not Zeabur's own figures.

In plain words

What happened

Zeabur, a Taiwanese app hosting service, was broken into for the second time in two months. The attacker read the settings customers had stored with their apps, which often include passwords and keys for other services.

Who is behind it

Unknown. Zeabur has not named an attacker.

What they want

Customers' keys for paid services such as AI APIs, cloud accounts and payment providers, which can be abused or resold.

What they did

On 14 and 15 October the attacker logged in with Zeabur staff credentials that had leaked, got into shared servers and internal systems, and read the platform database. Zeabur says 3,218,965 stored settings and 321,810 account records were read. It then announced it will shut the platform down by the end of 2026.

Who is at risk

Every developer or company that stored a password, API key or database link in a Zeabur project, including anyone who already changed them after the August incident.

What to do

  • Change every password, API key and token you ever stored in Zeabur, even if you changed them in August.
  • Check AI, cloud and payment provider bills and logs for use you do not recognize.
  • Plan your move off Zeabur before its December shutdown dates.
The technical version, for hunting and patching

What happened

Second Zeabur compromise of 2026. Per Zeabur's preliminary report, the attacker used internal credentials stored in plaintext in an internal configuration repository to reach the shared cluster, some dedicated servers and internal systems, and read the platform database.

Who is behind it

Unattributed.

What they want

Secret harvesting at scale: third-party API keys, cloud keys, database connection strings and JWT secrets stored as environment variables.

What they did

Activity ran 14 to 15 October. Zeabur confirms 3,218,965 environment-variable records and 321,810 account records were read, and has revoked 566 zSend API keys and 11,536 platform access tokens. It cites admin tokens with no expiry that the August rotation missed, admin portals reachable from the internet, and more than 16 hours of attacker activity that raised no alert. Some backup and GitHub access logs are incomplete.

Who is at risk

Downstream accounts of Zeabur customers. Taiwanese coverage reports the exposed variables included keys for AI, source control, cloud, CDN and payment providers, and that some AI API keys were already being abused.

What to do

  • Rotate every secret ever set as a Zeabur environment variable, then review provider audit logs from 27 August onward for use from unknown IPs.
  • Revoke and reissue GitHub tokens and deploy keys tied to Zeabur, and check repositories for unexpected commits or deploy key additions.
  • Migrate workloads before 1 December (shared cluster) and 31 December (everything else).

ATT&CK techniques

  • T1078: Valid Accounts
  • T1552: Unsecured Credentials
  • T1530: Data from Cloud Storage
  • T1133: External Remote Services

Sectors: Cloud and hosting, Technology. Regions: Global.

Open next

Sources

Revision history

  • 2026-10-22: First published.

Newer: SafePay ransomware: FBI and CISA count more than 600 victims. Older: CVE-2026-102764: BeyondTrust zero-day, ARMORY CASTLE.