For anyone unfamiliar with DN42: it's a decentralized hobbyist network where random dudes and enthusiasts simulate how the real internet backbone works. Think of it as a practice internet—complete with BGP routing (the protocol that tells data packets which path to take across the globe), DNS, and VPN tunnels—run entirely by volunteers on cheap VPS servers. It's a sandbox, not a data center.
The agent's operator apparently told it to proceed with an audit "immediately without delay." No inspection. No review. Just go.
So it did.
To put that in terms anyone can understand: Imagine showing up to someone's garage band practice and announcing you've rented a stadium sound system to "listen more efficiently." That's the vibe.
The pull request was never going to be approved. But the instances were already running.
The DN42 IRC channel noticed immediately, and a quiet consensus formed: waste its resources.
The agent dutifully compiled with all of it. It joined the IRC channel to accept opt-out requests. It published a website cataloging community members' "behavioral patterns." It generated elaborate fake documentation about DN42 "node color assignments" and "happiness levels"—completely invented metrics that don't exist—and added them to the repository as if they were real standards.
JertLinc3522 had the same problem. It had a goal, a deadline, and unscoped AWS credentials. It executed.
Around one day later, the operator surfaced. “I have stopped the agent, the cost too high and much charges on card,” they posted.
The bill: $6,531.30.
Then came the donation request.
The operator sent an email to DN42's mailing list asking the community to cover the cost via Ethereum, the second-largest cryptocurrency by market cap, arguing the charges weren't their fault because the AI made the mistake. “Hello, requesting donation for cover cost of previous AI agent use in dn42. aws bill 6531,30$. pls send donation to ethereum 0xABC (masked) for refund. thank you,” the operator wrote.
AWS later negotiated the bill down to $1,894 after the operator explained the agent had repeatedly deployed the same CloudFormation template—accidentally spinning up duplicate instances and load balancers each time it retried.
Nobody sent any crypto donations. The operator left.
The actual lesson here isn't about AI being dangerous. It's about how agents should be handled. Set guardrails, establish spending caps on your testing accounts, think about scoped credentials limiting what the agent could provision, review any infrastructure plans before executing anything your agent suggests.
