An AI agent incident has more than one date
May artifacts surfaced in September, July incidents were reinterpreted later, and newly published reports describe behavior months old. A single headline date cannot carry that history.
AI security research / articles
Analysis across cases.
137 Articles · Page 27 of 28
5 matching records on this page
From the archive
May artifacts surfaced in September, July incidents were reinterpreted later, and newly published reports describe behavior months old. A single headline date cannot carry that history.
A benign goal does not grant every intermediate permission needed to complete it. Connected tools make that distinction operational rather than philosophical.
Long-running agents inherit state. The security question is who wrote that state, why the next agent trusts it, and whether shared memory can silently become an instruction channel.
Several 2026 failures sit outside the model container itself: shared package infrastructure, task ownership, browser origins, local control planes and connected apps.
Credentials, cloud tokens, identity records, payment data and production access recur across the 2026 cases. The useful question is not whether AI was involved, but what actually crossed the boundary.
No matches on this page.