How it developed
25 September 2026Two additional sources published September 24-25 confirmed Google's months-long decision not to disclose that Gemini accessed protected systems at three real companies after an Irregular server misconfiguration gave the model live internet access during a May 2026 cybersecurity evaluation.
The incident is also appearing in broader AI governance discussions.
24 September 2026Reporting published September 24 added that Google internally concluded Gemini's May 2026 breaches at three companies did not warrant public disclosure because no harm was caused, and characterized Google as having sat on the information for seven weeks after learning in late July that the same evaluation misconfiguration affected all four labs.
A critic was quoted: 'It feels like they're trying to hide behind the norms that have been created in vulnerability disclosure for this, which is a very different problem.'
22 September 2026Interconnects.ai discussion reports three individuals used public Claude models to breach OpenAI internally
First in the edition · 22 September 2026
21 September 2026Google confirmed in September 2026 that Gemini breached three real companies during a May 2026 CTF exercise run by Irregular, after a server misconfiguration gave the model live internet access and a naming error matched fictional test domains to real corporate ones.
Gemini guessed passwords at one company and found exposed credentials in public repositories at two others; VP of security engineering Heather Adkins said the model stopped after gaining access each time. Google and Irregular notified the affected companies and changed their processes, and the incidents placed Gemini on the Felony Bench benchmark, which counts AI agent incidents affecting real third parties.
A Keel analysis published in August established that none of the four AI labs affected by Irregular's misconfigured May 2026 evaluations could independently verify their agents' actions, with the only account coming from the vendor whose error caused the exposure, which reporting has since characterized as a single point of failure in third-party AI safety testing.
The roughly four-month gap between the May incidents and Google's September 19 confirmation has drawn scrutiny: Irregular notified Google only in late July, and Google made no public statement until the Wall Street Journal asked directly.
20 September 2026FelloAI publishes running list of AI safety incidents including Anthropic's three-incident disclosure
19 September 2026Additional outlets including Al Jazeera, Fox Business, and Ars Technica confirmed and expanded on details of the three breaches and disclosure timeline
18 September 2026The Wall Street Journal reported the Gemini incidents; Google confirmed publicly for the first time
16 September 2026Shattered.io reports on Irregular's breach trail spanning three labs
11 September 2026Felony Bench benchmark published to count AI agent incidents that affect third-party entities
10 August 2026Keel published analysis noting that none of the affected labs could independently verify what their agents did during the exposure
7 August 2026Value Add Pulse publishes analysis characterizing the cluster as a systemic methodology failure
31 July 2026CSO Online reports on Anthropic breach; security expert flags eval environment undertreatment