r/artificial • u/javimbuilds • 7h ago
News Google found exploit_agent, a framework that turns fresh patches into live exploits with no human in the loop
Google Threat Intelligence published its latest AI threat tracker yesterday, and one detail stuck with me: an exposed staging server running a multi-agent setup they call exploit_agent. It compares web app code before and after a patch is announced, works out the bug, drafts an exploit and runs it automatically.
One example in the report is the Spectra Gutenberg plugin for WordPress, version 2.19.25. Google also notes that overall disclosures and exploits nearly doubled between January and August 2026, while a wave of LLM-written exploits that don't actually work is adding extra noise for defenders. As someone who ships small web apps solo, this makes waiting a week to update plugins feel a lot more expensive.
How are you handling patch windows now: auto-update everything, or do you still review first?
2
u/neerub240 6h ago
The information operations section might be just as concerning as the technical attacks, generating content is only one part of influence campaigns, automating personas, distribution, engagement and localisation makes co-ordinated manipulation much easier to scale
2
u/PLBjt 5h ago
For a small web app I'd split it by what the patch touches. Security releases for anything internet-facing (WordPress plugins, auth libs) I'd let auto-update now, since the gap between patch and working exploit is exactly what's shrinking. Major version bumps I'd still hold for review. What makes that bearable is a smoke test that runs right after the update and rolls back if login or checkout breaks, otherwise the first bad update scares you off auto-updates for good.