BRIEF NO. 001 BreachAI credentials
NEW BRIEF EVERY WEEK

Is your site exposed to AI attackers?

Plain-English briefs on AI-driven attacks, and the fixes to make on your own site this week.

The OpenCode breach explained: what was exposed and what to rotate

What happened, whether your workspace is affected, and which credentials to rotate this week.

Plain EnglishSources on every claim

01 – 02
Latest briefs
51% of web traffic in 2024 came from bots
Imperva 2025 Bad Bot Report
80–90% of the GTG-1002 hacking work was done by an AI agent
Anthropic, Nov 2025
~30 organisations targeted in that one campaign
Anthropic, Nov 2025

What we cover

The attacks business owners now face, each with an explainer and a fix.

01 Leaked AI API credentials

Revoke, rotate, check usage, then find the leak. Plus how to store keys so it doesn't happen again.

Explainer and fix →
02 Distillation attacks

Someone queries an AI model at scale to train a cheaper copy of it, often on your account.

Explainer and fix →
03 AI penetration testing

Automated attackers find weak spots faster. The same tools can check your own site first.

Explainer and fix →
04 AI bots and crawlers

Which bots to allow, which to block, and how to stay visible in AI search.

Explainer and fix →
05 Prompt injection

When your chatbot or agent takes orders from a stranger's text.

Explainer and fix →
06 WordPress and PHP patches

Updates, plugins and versions to check now that AI finds bugs faster.

Explainer and fix →

Latest from the lab

See everything →
A developer lit by the glow of code on a screen LEARN What is a distillation attack? Explained for business owners How stolen API access is used to copy an AI model, and why the bill lands on you. By Tommy D · Updated 28 October 2026Read → See everything →

Start with your situation

Written by people you can check up on.

Every guide is written by Tommy D Every claim is sourced, every update is dated, and corrections are made in public.