AI Agents Now Hack Without a Human. Google Just Caught One Doing It.

Google says attackers have crossed a line: AI agents that compare a security patch with the old code, find the flaw, write the exploit and launch it, with no human involved. ARTEX is already the subject of an FBI alert. The intrusion mechanics have not changed, but their speed has. Here is what Google found and how to respond.

For information only. This article is based on Google Threat Intelligence Group (GTIG) and Mandiant findings published on November 17, 2026, as reported by Help Net Security and SecurityWeek. TechVernia has not reviewed the original report or the FBI alert directly and has no commercial relationship with the companies mentioned.

The Human Just Left the Attack

For years, the security industry has warned that AI would one day run cyberattacks on its own. On November 17, 2026, Google said that day has arrived.

Google Threat Intelligence Group (GTIG) reported that, in the past quarter, it saw threat actors use AI frameworks to discover and exploit vulnerabilities without a human in the loop, for the first time. GTIG calls it "a paradigm shift towards intrusions occurring at machine speed."

The attacks themselves are not new. What changed is who runs them, and how fast.

0 Humans needed to turn a new patch into a live attack, in one operation found by GTIG
5+ AI attack frameworks seen in use: ARTEX, CAIRN, CyberStrikeAI, PentAGI, HexStrike AI
22 Zero-day exploits counted in August 2026, against a 2025 average of 8 per month
$1M Worst LLMjacking case: stolen AI and cloud access abused before it was stopped

Inside exploit_agent

The clearest case came from an exposed staging server. On it, GTIG found a framework its operators called "exploit_agent": a multi-agent system connected to several frontier and local AI models.

Its workflow is short:

StepWhat the agents do
1. DiffCompare a popular web application's code before and after a security patch is announced.
2. FindIdentify the vulnerability the patch was written to fix.
3. WeaponizeDraft a working exploit for that vulnerability.
4. LaunchRun the exploit against real targets, with no human approval in between.

The same server held stolen victim data, brute-force scripts and tools to install and remove webshells. Configuration comments were written in Russian, and one label read "for auto-exploitation (exploit_agent pilot)." Victim telemetry pointed to French websites in media, entertainment and education.

This technique has a name: patch diffing. Human researchers have done it for decades. It is slow, skilled work. It is also exactly the kind of task large language models do well: read two versions of code, explain what changed, and write code that uses the difference.

Not One Tool, an Ecosystem

exploit_agent is not alone. GTIG and Mandiant saw attackers using several AI offensive frameworks, some of them open source, and some groups building their own.

FrameworkWhat was reported
ARTEXThe most used, mainly by Chinese-speaking groups. The FBI issued a FLASH alert on November 13, 2026: in use since at least August 2026 against financial services, government, technology, defense, healthcare, energy and other sectors.
CAIRNUsed in activity targeting the US aerospace sector.
PentAGIUsed for systematic reconnaissance and vulnerability scanning across organizations in Asia.
CyberStrikeAI, HexStrike AIAlso observed in attacker operations.
Custom frameworksGTIG saw a China-nexus group building its own automated attack framework, likely for espionage.

According to the reporting, these tools can find and exploit simple vulnerabilities and adapt their tactics based on how a target responds.

The Patch Window Is Closing

Most vulnerability management programs rest on one quiet assumption: after a patch is released, defenders have time. Attackers need days or weeks to reverse engineer the fix and build a reliable exploit. Defenders patch in between.

AI breaks that assumption. GTIG notes that automating vulnerability analysis and exploit development lets threat actors shorten the time between a patch's release and its active exploitation. The broader numbers point the same way: GTIG's September analysis found that vulnerability disclosures and exploits nearly doubled between January and August 2026.

A monthly patch cycle is now a monthly exposure window. If a working exploit can appear within hours of a fix, an internet-facing system patched "next maintenance window" stays open to automated attacks for weeks. Organizations that still patch monthly, such as hospitals, water utilities and regional energy providers, carry the most risk.

There is a side effect too. After patches for two PHP flaws (CVE-2026-109618 and CVE-2026-109619) landed on October 21, hundreds of non-functional proofs of concept appeared online. The security community had to check each one. AI does not only speed up attackers. It also floods defenders with noise.

LLMjacking: Your AI Bill as the Target

The same reporting describes a second trend: attackers stealing access to AI itself. Mandiant responded to several LLMjacking incidents in 2026, where attackers hijacked cloud environments to consume the victim's compute and AI model quotas.

For any company running AI workloads in the cloud, an exposed API key is no longer just a data risk. It is a direct financial risk.

The Good News

01
Same mechanics

The Attacks Still Need the Same Doors

GTIG stresses that the mechanics of intrusions have not changed. These agents still abuse unpatched systems and compromised credentials. Every control that closes those doors still works against an AI attacker.

02
Speed is noisy

They Trade Stealth for Velocity

According to GTIG, these frameworks generate traffic and code traces that make them easier to detect. An agent that tests exploits at machine speed leaves a loud trail. Teams that watch their logs have a real chance to catch it.

What to Do Now

ActionWhy
1. Patch internet-facing systems in daysPrioritize anything exposed to the internet. The window between a fix and a working exploit is shrinking fast.
2. Watch the days after a patchExpect bursts of exploit attempts right after a vendor releases a fix. Raise monitoring on affected systems until they are patched.
3. Lock down credentialsEnforce MFA, remove unused keys, and rotate any exposed cloud or AI API key. Set budget alerts so LLMjacking shows up as a cost spike, not a surprise invoice.
4. Automate detection and responseMachine-speed attacks need machine-speed defense. Automate the first response steps for the most common alerts.
5. Hunt for the noiseLook for rapid, repeated exploit attempts and webshell activity on web servers. Automated attackers rarely slow down.

The Fine Print

What to read with care. This article relies on press coverage of Google's findings, not on the original GTIG report or the FBI FLASH alert, which TechVernia has not reviewed directly. Details such as attribution and victim sectors come from Google and the FBI as reported. The CVE identifiers mentioned are cited by Help Net Security. Check the original sources before making security decisions.

On November 17, 2026, Google Threat Intelligence Group reported that attackers are now using AI frameworks to discover and exploit vulnerabilities without a human in the loop, including a system called exploit_agent that turns new security patches into live attacks. The mechanics of intrusion have not changed, but their speed has, and a monthly patch cycle is no longer fast enough for internet-facing systems.

Frequently Asked Questions

What did Google find?
Google Threat Intelligence Group saw threat actors use AI frameworks to fully automate vulnerability discovery and exploitation, without human involvement, for the first time. One framework, exploit_agent, compared code before and after security patches, built exploits and launched them.
What is ARTEX?
An AI-driven offensive framework that GTIG describes as the most used, mainly by Chinese-speaking groups. The FBI issued a FLASH alert about it on November 13, 2026, warning that it has been used since at least August 2026 against many sectors.
What is patch diffing?
Comparing software before and after a security update to find the vulnerability the update fixed. Attackers then target systems that have not installed the update yet.
What is LLMjacking?
Stealing credentials to use a victim's AI models and cloud compute. The victim pays the bill. Mandiant saw cases reach $1 million.
Can AI-driven attacks be detected?
Yes. According to GTIG, these frameworks trade stealth for speed and leave noisy traffic and code traces. Good logging, monitoring and fast patching remain effective.

My Take

AI did not invent a new type of attack. It removed the slowest part of an old one: the human. Patch diffing, exploit writing and scanning used to take skilled people days. Now they take an agent hours.

As a network security engineer, I read this report as a deadline, not a headline. The basics still win: patch what faces the internet, protect credentials, watch the logs. But they now have to run at the attacker's speed, which means automation on the defender's side too.

How fast can your team patch a critical internet-facing flaw today?

Sources:

This article is published for information purposes only, to help readers understand AI-driven threats and how to defend against them.

Related Articles:

Kodjo Apedoh

About the Author

Kodjo Apedoh

Network Engineer & AI Entrepreneur

Founder of TechVernia & SankaraShield. Certified Network Security Engineer with 4+ years of experience specializing in network automation (Python), AI tools research, and advanced security implementations. Also builds iOS and Android applications. Holds certifications from Palo Alto Networks, Fortinet, and Cisco. Based in Arlington, Virginia.

Connect on LinkedIn →