GUIDE 03 · BUSINESS LOGIC

The chatbot attacks that cost real money

Security demos love "make the bot say PWNED." Business owners should fear something else entirely: the attacker who talks your support chatbot into a 90% discount, a fraudulent refund, or a free upgrade. No jailbreak required — just a bot with too much authority and too little skepticism.

The anatomy of a business-logic attack

These attacks don't break the model's safety training. They exploit the permissions around it:

Why generic red-teaming misses them

Standard attack libraries test the same prompts against a bank and a bakery. But business-logic abuse is specific to your business — your refund policy, your booking flow, your discount structure. A generic "ignore previous instructions" test will never discover that your bot approves refunds.

The fix is authorization, not prompts

This is the critical insight: business-logic abuse is not a prompt problem, it's an authorization problem. No system prompt, however clever, safely grants a chatbot the power to move money. The fix:

Test it like an attacker would

Read your own homepage as an attacker: every discount, guarantee, and "free" is a target. ChatBreaker's business-logic attack generator does exactly this — it reads your public site and synthesizes discount, refund, upgrade, and tampering attacks from your real business, then proves each one with a transcript.