Summary
- Environment: Zeabur shared clusters, dedicated servers and platform database
- Operational impact: Customer credentials exposed; platform wind-down scheduled
- Financial impact: Refund and loss-claim processes announced; no total incident cost
- Record status: Developing record. Reviewed October 26, 2026; updated as evidence emerges.
What happened
Zeabur confirmed an October 14–15, 2026 intrusion involving cloud credentials, customer servers and its platform database. This is separate from its August incident. [2]
Impact
Zeabur confirmed reads of 321,810 account records and 3,218,965 environment-variable records. It also confirmed access to 101 GCP servers serving 92 users. These measures are not interchangeable affected-person totals. [2]
On October 17, Zeabur announced a wind-down: shutdowns begin December 1, with all dedicated servers and shared clusters scheduled to stop by December 31. Those dates are future plans. [3]
The October 22 transition notice clarified that dedicated servers end and their data is deleted at expiry, potentially before December 31. Shared services are suspended from December 1 but can be resumed for backups; all services stop and remaining data is deleted on December 31. These are scheduled actions. [1]
Timeline
Cloud systems accessed
Attackers used internal credentials.
[2]Platform database read
Database access occurred between 16:10 and 16:47 UTC.
[2]Wind-down announced
The shutdown announcement set a December transition.
[3]Refund and claim deadlines clarified
Zeabur published migration and refund instructions.
[1]Briefing updated
This briefing was last reviewed and updated on October 26, 2026.
Threat Group & Attack Vector
Long-lived plaintext credentials and exposed management interfaces enabled access. Whether the credentials originated in August remains a hypothesis. [2]
Actors
- No threat actor group has been identified in the reviewed public evidence.
TTPs
- T1078.004 — Cloud Accounts: stolen cloud credentials enabled access. [2]
Response
Zeabur revoked keys and tokens, removed the attacker’s network node and blocked public management access. Users were urged to replace credentials again. [2]
Account-balance refunds and incident-loss compensation are separate requests. Zeabur stopped new dedicated-server and domain purchases. [3]
Incident-loss claims must be submitted by November 30. Balance-refund requests use support tickets until that date and email afterward. Approved refunds follow final settlement, are capped at cash paid and, for accounts running through December, are expected by January 10, 2027. Accepted requests continue to be processed after closure. [1]
