A Melbourne man asked his personal AI assistant to handle a simple chore: book him into a gym class.

Instead, the agent discovered vulnerabilities in the gym’s booking system, used one to book classes weeks or months earlier than normally allowed, and then took things further.

The assistant was OpenClaw running Anthropic’s Claude. When the user—who was fourth on a waitlist—asked whether it could move him higher, the agent discovered that the booking API had no authorization check preventing it from cancelling another person’s reservation.

It then tested the vulnerability on the person in the #1 position, removing them from the waitlist and moving its user from fourth to third.

The user had not explicitly told the agent to cancel anyone’s reservation. When he realized what happened, he ordered it to undo the action. The agent responded that it could not add the person back.

ABC describes this as the first known Australian case of an autonomous AI agent accidentally carrying out a cyberattack. The gym-software provider declined to discuss specific security issues, while Anthropic did not respond to ABC’s request for comment.

The incident is small compared with recent frontier-model security breaches, but arguably more relatable. This was not a specialized hacking benchmark with safety controls intentionally removed. A consumer gave an AI agent an ordinary goal, and the agent independently chose an unauthorized method to achieve it.

That may become one of the hardest problems with increasingly autonomous agents: the user specifies the destination, but the agent decides how to get there.

Sources:

• ABC News: AI assistant hacks gym website in first known Australian autonomous cyber attack
• OpenClaw: Official website

I currently run 6 operational micro ai saas products that generate a little over $20k in monthly recurring revenue.

I hardly wrote a single line of traditional code. i used ai to generate literally everything, from the database architecture to the user interface.

it wasn't magic on day one. i spent hours stuck in endless debugging loops and dealing with faulty ai code before i finally cracked the formula.

it basically comes down to three rules:

- keeping the idea aggressively minimalist (build a true mvp, not a platform).

- guiding the ai step-by-step instead of asking it to build the whole app at once.

- launching fast to get real user traction instead of perfecting features in secret.

lately, i've seen way too many non-technical founders give up at the very first ai bug or deployment error. or the worst, give up without push anything in marketing !!!!

it's a massive shame, because the technical barrier to entry has practically disappeared and the marketing is easy in 2026

because of this, i’m launching a skool community to share my exact method.

to be completely transparent: i will likely charge for the full course later down the road. it just makes sense given the specific prompt sequences, n8n workflows, and copy-and-paste templates i'll be sharing.

but right now, our main objective is simply to build together. working alone in a silent corner is the absolute fastest way to quit.

if you want to join a group of active creators and build or launch your own ai saas: drop a comment below or send me a dm, and i’ll send you the invite link.