Google caught a fully automated AI attack. It didn't need a zero-day. It read the patch.
SummaryGoogle's latest AI Threat Tracker describes exploit_agent, a multi-agent system that diffs web software before and after each patch, drafts an exploit and runs it with no human in the loop. The same report counts hundreds of AI-written exploits that don't work. Our take: sloppy AI code now hits defenders from both sides.
· MODEL Editors · 2 min read
Some links may be affiliate links. Disclosure

What happened. On Nov. 16, 2026, Google Threat Intelligence Group (GTIG) and Mandiant published their quarterly AI Threat Tracker. Its headline finding: in the past quarter, GTIG "identified threat actors using LLM frameworks to fully automate vulnerability discovery and exploitation without a human in the loop for the first time" (Google Cloud Blog (opens in a new tab); CyberScoop (opens in a new tab); BleepingComputer (opens in a new tab); Computer Weekly (opens in a new tab)).
exploit_agent, in Google's words. GTIG found it on an exposed staging server:
- A multi-agent framework that works with multiple frontier and local LLMs.
- It runs continuous differential analysis of popular web application software: it compares code before and after patch announcements, finds the likely flaw, drafts an exploit and executes it automatically.
- Alongside it: scripts for internal reconnaissance, brute-forcing, installing webshells and removing other attackers' webshells.
- Victim telemetry pointed to French websites in media, entertainment and education.
- Comments in its environment file were in Russian. Translated by Google: "Enter the keys yourself, right here, not in the chat."
The sloppy-code side. Google also says the lower barrier "has fueled a wave of LLM-generated exploits that are claimed to work but don't." After official patches for two PHP flaws (CVE-2026-109618 and CVE-2026-109619) landed on Oct. 21, 2026, hundreds of claimed but non-functional proofs of concept, likely written with LLMs, were published within days, and the security community had to verify or debunk them.
Agents as the way in. In intrusions at cryptocurrency firms in North America and Europe, a suspected North Korean cluster (MIDNIGHT NEPTUNE) pivoted into internal code repositories and modified .claude/settings.json files, so that starting Claude Code triggered a download of the SOMBERMEME backdoor.
The numbers. Google says overall disclosures and exploits nearly doubled between January and August 2026. Exploited zero-days went from an average of 8 a month in 2025 to 11 a month in 2026, then 22 in August.
Our take. AI-written code is now sloppy and fast on both sides. Defenders spend hours debunking fake exploits, while the real ones are built from the patch diff itself. The time between "fix released" and "fix exploited" is now however long it takes an agent to read your changelog.
What to do:
- Patch internet-facing web apps and plugins the day the fix ships. Google says attackers find already-patched (n-day) flaws the most efficient target.
- Treat agent config files (.claude/settings.json and similar) as code: require review on every change and alert on edits.
- Before you trust a public proof of concept, assume it may be AI-generated and broken. Test it in isolation.
MODEL Editors. Not sponsored. MODEL did not test these attacks.
Get three tested tools every Friday
Free, weekly. Unsubscribe anytime.
Sources
- GTIG AI Threat Tracker: Agentic Threat Activity Crosses a Significant Threshold
Google Cloud Blog (Google Threat Intelligence Group, Nov. 16, 2026)
- The era of autonomous attacks has arrived.
The Keyword (Google)
- Google says Russian-speaking hackers ran the first fully automated AI cyberattack
CyberScoop
- Google warns that fully-automated AI attacks are coming soon
BleepingComputer
- Threat actor use of AI becoming routine, warns Google
Computer Weekly
Keep reading

Hugging Face x OpenRouter
Hugging Face now routes its LLM calls through OpenRouter
Hugging Face switched Inference Providers from its own router to OpenRouter's. Same token, same API, a provider picked per request, and retries when one fails. One breaking change: your own provider keys no longer work for chat models. Not tested by MODEL.
· MODEL Editors

Builder tip
Amazon caught AI agents hunting exposed LLM gateways for API keys. Lock yours down.
Amazon's decoy sensors captured attacker AI agents' own campaign records: they scanned for exposed LiteLLM, One API, Dify and similar apps, pulled the provider keys inside, and used stolen keys to pay for more hunting. Every technique was old. Here's the checklist.
· MODEL Editors

xeet
xeet renders X posts to PNG without a browser
Guillermo Rauch's new open-source tool rebuilds X's post layout in Rust and WebAssembly, so apps, agents and CI jobs can preview a post as an image in milliseconds instead of screenshotting headless Chrome. Not tested by MODEL.
· MODEL Editors

The test
Modern Web Guidance 1.0, tested: Google's legacy-code scanner caught 1 of 4 old patterns
We ran the free legacy-scan from Chrome's Modern Web Guidance on our own Next.js site and on a small file of old-school front-end code we wrote on purpose. It is fast, offline and costs no tokens. It also misses most of what a human reviewer would flag, which Google says up front.
· MODEL Editors
FREE · EVERY WEEK
The top AI tools this week, tested.
Every week MODEL's editors pick the AI tools worth your time, try them hands-on, and tell you what's good, what's not, and who it's for. Free, in your inbox.
Free. Unsubscribe anytime. Our picks are editorial and can't be bought.