Google reports attackers now using AI agents to automate real-world intrusions
Compiled by RedTeamDaily · AI-assisted summaries · Human review not recorded for this version
Published
What happened
GTIG and Mandiant report threat actors using or testing multi-agent frameworks ARTEX (used in real intrusions), CAIRN, PentAGI, CyberStrikeAI and HexStrike AI. PaperCut flaws CVE-2026-81578 and CVE-2026-82078 were exploited as zero-days in August 2026, and GreyNoise reported an AI-assisted campaign reaching domain admin within minutes. Google SecOps has released behaviour-based detection rules for ARTEX. Defenders should restrict admin systems, use short-lived credentials, set AI service budget alerts, scan code for leaked keys and monitor spikes in API and identity activity.
For security analysts · Written by AI from 1 source · Report an error
- Exploitation
- Reported in CVE data
- Sources
- 1
Affected products and technical context
These linked CVE records are maintained separately from the source summary above. They may supply affected versions or fixes that the original report did not include. Confirm the correct release branch with the vendor.
CVE-2026-81578
Exploitation: CISA KEV listed — known exploitation reported by CISA.
Affected products: Not yet available in our structured data. Check affected version ranges.
Fixed releases: Not yet available in our structured data; consult the vendor advisory.
Choose the fix for your release branch. CVE record · NVD record
CVE-2026-82078
Exploitation: CISA KEV listed — known exploitation reported by CISA.
Affected products: Not yet available in our structured data. Check affected version ranges.
Fixed releases: Not yet available in our structured data; consult the vendor advisory.
Choose the fix for your release branch. CVE record · NVD record
Sources and editorial review
No named human review has been recorded for this story. See the source evidence below.
No vendor or government source is linked to this story yet. Read the source reports; attribution is not independent verification.
How severity and exploitation labels work · All source reports · Report an error
What to do
- Lock down admin systems and use short-lived credentials to limit access.
- Set budget alerts for AI services and scan code for leaked keys.
- Treat any unexpected AI service activation as a serious warning and investigate it.
- Watch for sudden spikes in API and identity activity and deploy Google SecOps ARTEX detection rules where applicable.
Written by AI from the sources, checked against them
Source timeline (UTC) · 3 updates
Explore this report
Check my watchlist Requires sign-in · matches your saved products without AI.
Ask AI about this story
Optional follow-up answers generated from our coverage. Check the linked sources before acting.
Ask your own question