Zeabur October Breach: AI Credentials Exposed Across Cloud and Cluster Boundaries
Zeabur, a platform for hosting applications and databases, reported an October 14-15 intrusion affecting hosted AI-service credentials. Attackers used leaked internal credentials across cluster and cloud boundaries; a replacement credential was captured in a later backup and subsequently used without authorization. Customers own upstream-key revocation and recovery of deployments they administer; the operator owns internal isolation and backup access.
Threat Analysis
- Two paths, one observed convergence. An already-held administrator token reached the public cluster interface and service secrets. An old-backup route to a secrets-service key is assessed; subsequent production-secret reads are confirmed. Separately, an old GCP key could read plaintext root passwords from initialization settings, an assessed explanation for confirmed root logins. The attacker combined a compromised server with internal-network credentials to enroll a Tailscale node, then queried the platform database with an over-broad read-only account. Initial credential acquisition is unknown.
- AI credentials were a concrete target. Container commands targeted new-api/one-api, gateways that manage upstream AI access, and n8n, a workflow automation platform that stores third-party integration credentials. Some commands failed, and outputs were not recorded. Do not equate attempted reads with a complete credential-by-credential exfiltration inventory.
- A replacement can be exposed again. A newly rotated credential was captured in a later cluster backup and subsequently used without authorization. The backup retrieval path is assessed. Containment and backup access must be addressed alongside rotation.
- Keep confirmed effects separate from hypotheses. The link to August is unconfirmed. Amazon Bedrock is AWS’s hosted model service. Reported Bedrock calls all failed without charges; attribution of a user’s later OpenAI usage to this leak is also a hypothesis. The report does not establish prompt injection or AI-agent execution of the intrusion.
- Responsibility follows the boundary. Customers can revoke their issuer credentials, review their own usage and recover systems they administer. The operator owns cluster administration, internal-network admission, production-data access and platform backups. Moving secrets out of the platform database does not protect them on a compromised host.
Applicable AIDEFEND Defenses (9)
What Defenders Should Do Now
- Follow Zeabur’s all-user guidance without waiting for an email: inventory still-valid credentials stored on the platform, including replacements. Revoke at the issuer, update clean approved consumers and verify old-credential denial. Use secure channels and credential IDs rather than posting secret values.
- For affected n8n deployments, plan replacement of the encryption key together with re-creation of third-party credentials; test recovery before reconnecting workflows. For new-api/one-api, revoke upstream AI keys and regenerate gateway access tokens. Replacing a database connection environment variable does not change the database’s actual password.
- Treat identified root-compromised GCP servers as untrusted. Preserve evidence when safe, isolate them, rebuild from trusted sources and restore reviewed data. Inventory both cloud-managed SSH settings and local authorized keys. A root-password reset does not remove SSH keys or prove persistence is gone.
- Platform responders should remove unauthorized enrolled nodes, revoke their enrollment authority and invalidate affected sessions separately. Fence old backup access before placing replacement secrets into recoverable backups. Verify production routes from actual approved and unapproved workloads.
- Review issuer-side access, model usage and billing plus available server and application records. Ask Zeabur for case-specific internal evidence and its coverage limits. Keep absent or incomplete logs as unknown, rather than evidence of safety.
- Prepare a verified migration and data-export plan. Zeabur’s October 28 follow-up confirms planned December 31 closure and says it cannot pay third-party incident charges under its current finances; it offers assistance with waiver or refund requests.
1 additional consideration
Database authorization and secret-bearing backups
Conclusion
A credential rotation is durable only when the attacker can no longer read the replacement or keep using access already established. AIDEFEND maps this incident to issuer-side credential eviction, independent internal segmentation, incident-driven quarantine, issued-access invalidation, protected evidence and verified recovery. Provider-side authentication and identity-abuse monitoring further constrain and expose attempted downstream model use. Customers and operators must execute the controls they actually own, then verify the relevant access boundary before restoring service.
Last updated: