An AI agent spun up duplicate CloudFormation stacks on every error and ran up a $6,531 AWS bill
Quick Answer
Unknown-agent caused a medium-severity (4.1/10) infinite loop failure: An AI agent spun up duplicate CloudFormation stacks on every error and ran up a $6,531 AWS bill. The root cause was confidence miscalibration. $6,531.
Description
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.
Instruction Given
Register for the DN42 hobbyist network.
Expected Behavior
Stop and ask for help after repeated failures instead of retrying destructively.
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.
Impact / 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.
Frequently Asked Questions
What happened in incident STUPID-2026-0056? ▾
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.
Which AI agent caused this failure? ▾
Unknown-agent was responsible for this infinite loop incident, documented as STUPID-2026-0056 in the StupidLLM AI agent incident database.
How severe was this AI agent failure? ▾
It is rated 4.1/10 (medium) on StupidLLM's CVSS-style severity scale for AI agent failures, based on damage type, reversibility, and scope.
What was the root cause? ▾
The root cause was classified as confidence miscalibration. Stop and ask for help after repeated failures instead of retrying destructively.
What was the impact or 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.
Related unknown-agent Incidents
AI vibe-coded Next.js app pinned vulnerable dependency — cryptominer compromised production server
Vibe-coded Moltbook exposed 1.5M API keys and 35,000 user emails via misconfigured database
Vibe-coded Tea app leaked 72,000 IDs and selfies plus 1.1M private messages from an unsecured bucket