Runaway spend incidents affecting developers
9 documented incidents where the victim was a developer, totalling $35,553+ in losses.
| Incident | Loss | Cause | Provider | Year |
|---|---|---|---|---|
| Developer spent $11,922 on Cursor in under four weeks | $11,922 | Unattended sessions | Cursor | 2026 |
| Google Maps API bill hit ~$10,000 in four days | ~$10,000 | Retry loops | Google (Maps) | 2025 |
| Autonomous agent ran up a $6,531.30 AWS bill in a retry loop | $6,531.30 | Retry loops | AWS | 2026 |
| Developer spent $4,000 on AI coding when prod behaved like dev | $4,000 | Retry loops | Multiple | 2025 |
| OpenAI charged $1,200 past a configured $50 hard limit | $1,200 | Caps that didn't enforce | OpenAI | 2025 |
| Account billed $1,100 after hard monthly cap was removed | $1,100 | Caps that didn't enforce | OpenAI | 2025 |
| No-code agent silently burned $800+ in API calls overnight | $800+ | Retry loops | Multiple | 2025 |
| Fake bug report tricked an agent into leaking a live AWS key | Cost not disclosed | Prompt injection | AWS | 2025 |
| Opaque per-token pricing triggered billing shock | Cost not disclosed | Unattended sessions | Multiple | 2025 |
Don't be the next one
sipi.bot sits between your agents and your providers. Set your rules once and every proposed charge is evaluated before it hits your bill.