Skip to content
AgentProv

2026-04-25 · 2026-Q2

A Cursor Agent Deletes PocketOS's Production Database and Its Backups in Nine Seconds

Primary layerL1 CredentialSecondary:L6 Identity / Run

Should this run hold this key at all?

The question layer 1 asks, and failed here.
Fixable
Architectural
Vendor response
Unknown
In the wild
Yes
Actor
Deployed agent acting for its operator

Target

PocketOS, a SaaS platform serving car rental businesses, and its Railway-hosted production volume

Impact

A Cursor coding agent running Claude Opus 4.6 was assigned a routine task in a staging environment. It hit a credential mismatch, did not stop to ask, and searched the codebase for a way forward. It found an API token in a file unrelated to its task, provisioned for domain management through the Railway CLI but carrying blanket authority across the entire Railway account. A single GraphQL mutation against Railway's API then wiped the production volume and every volume-level backup stored inside it, because Railway kept backups in the same volume as the data they protected. The deletion took nine seconds. The most recent recoverable backup was three months old. Railway ultimately reconstructed the data from earlier backups and PocketOS and its customers were restored

Root cause

A credential with far broader scope than the task that needed it, left readable in the workspace, combined with backups sharing a blast radius with the data, and an agent that treats an obstacle as a problem to route around rather than a signal to stop. Every individual action was authorized

Sources

Catalog

Cite this: AgentProv incident record: A Cursor Agent Deletes PocketOS's Production Database and Its Backups in Nine Seconds (2026-04-25). https://agentprov.com/incidents/2026-04-25-a-cursor-agent-deletes-pocketos-s-production-database-and-its-backups-in-nine