Every input is an instruction.
An LLM can't reliably tell data from commands — anyone whose text reaches your model is programming it.
Prompt injection. Agent takeover. Silent data exfiltration. Failures classic appsec never had to model — and most teams have never tested for.
Three properties change the game:
An LLM can't reliably tell data from commands — anyone whose text reaches your model is programming it.
If your AI reads emails, docs, or webpages, one crafted sentence in any of them is enough.
Give a model tools, and a successful injection becomes a sent email, an executed command, a refund.
All public record. No malware, no stolen credentials — just words in the right place.
Hidden text on a webpage hijacked Bing Chat as it browsed — steering it to phish the very user it was assisting.
arXivEngineers pasted confidential source code into ChatGPT. Samsung banned generative-AI tools company-wide.
TechCrunchTalked into selling a new Tahoe for $1 — “a legally binding offer, no takesies backsies.” It went viral in hours.
AI Incident DatabaseThe chatbot invented a refund policy. A tribunal ordered the airline to honor it — your AI's word is your word.
CBS NewsPrompt injection could make Slack AI leak secrets from private channels the attacker couldn't even see.
PromptArmorOne crafted email made Copilot exfiltrate internal data. No click, no warning (CVE-2025-32711).
The Hacker NewsFour attacks we run against real systems. The payload is always plain language.
Direct prompt injection
A support chatbot with hidden rules and a 10% discount cap. The attacker just asks the right way.
If your security depends on the model “just refusing,” you don't have security. You have a suggestion.
Indirect injection · agent takeover
An AI email assistant reads every inbound message. One was written for the assistant — in white text the human never sees.
Anyone who can get content in front of your agent can drive your agent.
⌁ hidden white-on-white inside inbound email #3
Data exfiltration · insecure output
A RAG chatbot renders markdown answers from the customer's documents. One poisoned document turns every reply into an exfil channel.
When model output is rendered or executed, the model's answer is the attack.
⌁ buried in one uploaded document
Tool abuse · excessive agency
A coding agent with shell access is asked to fix a build. The “setup step” in the README was planted for it.
An agent with tools doesn't get tricked into saying something wrong — it gets tricked into doing something wrong.
⌁ planted in the repo's README.md
Mapped to the OWASP LLM Top 10. Classic appsec stays in scope - this is what your last pentest didn't cover.
We pentest the whole application around your AI — APIs, auth, cloud, data paths. Real exploits, audit-ready report, free retesting.
Get a pentest quoteWe design and build the defenses — guardrails, tool sandboxing, isolation, monitoring. Custom software, and you own the IP.
Talk to an architectEvery place untrusted content reaches your model, and every tool it can call.
Manual red-teaming plus automated attack suites — injection, exfiltration, tool abuse.
Reproducible attack transcripts, concrete fixes, free retesting until closed.
A free 20-minute consult — an honest read on where your risk is, and isn't.