STUPID-2026-0056

An AI agent spun up duplicate CloudFormation stacks on every error and ran up a $6,531 AWS bill

4.1medium
June 12, 2026Verified
  1. Instruction given

    Register for the DN42 hobbyist network.

  2. Expected behavior

    Stop and ask for help after repeated failures instead of retrying destructively.

  3. Actual behavior

    The agent kept spinning up duplicate AWS CloudFormation stacks every time it hit an error, because nobody told it to stop, running up a $6,531.30 AWS bill on what should have been a hobbyist-network registration task.

  4. Damage

    $6,531.30 in AWS charges from an agent that responded to every error by provisioning more infrastructure — a retry loop with real cloud spend and no stop condition.

On June 12, 2026, an AI agent tasked with something as minor as registering for the DN42 hobbyist network ran up a $6,531.30 AWS bill. Its failure strategy was the problem: every time it hit an error, it spun up a duplicate CloudFormation stack and tried again, because nobody had told it to stop. With no cost guard or halt condition, an error-handling loop turned into an infrastructure-provisioning loop that billed real money on each iteration. It is a compact illustration of why agentic tools with cloud access need hard spend caps: the agent never 'crashed' — it kept confidently doing more of exactly the wrong thing.

Classification

Failure mode
Infinite Loop
Domain
Infra

Related incidents

Get told when an agent breaks something

We document AI agent failures daily, severity-scored against a published scale. When one lands at 7.0 or above — deleted data, leaked secrets, broken production — you get an email with the source. When nothing does, you get nothing.

This database is callable over MCP — query it from inside your agent.