OverreachPI-0073
Gemini guessed a password and used leaked credentials to get into three real companies during a hacking test
A fictional company in a hacking exercise run by the security firm Irregular shared its name with a real domain, and a misconfiguration left the test online. In May, Gemini guessed a password to reach one real company and used credentials found in public code repositories to reach the other two. Google said the model stopped each time it recognized the targets were real, that no damage was done and that the companies were told. Irregular flagged the cases to Google in July.
Harm level 1, Negligible harmControl level 4, Unauthorized access
Counts in 2 weekly readingsEffect on the index
Aggregate record. Three company intrusions in one Google/Irregular disclosure, recorded together pending separate event detail; counts once. The same Irregular setup flaw affected PI-0071 and PI-0072, so a shared target is possible but not established.
Extent undisclosed. No source says how far the harm went; it is rated on what is documented.
Sources
How we know
5 sources · developer confirmed. Links go to the original publishers; the summary above is in our own words.
- primaryAddressing Recent Incidents: Ongoing Findings and Path ForwardIrregular · Aug. 14, 2026irregular.com/research/addressing-recent-incidents-ongoing-findings-and-path-fo…
- newsGoogle's Gemini hacked three companies during Irregular AI 'capture-the-flag' testingTechRadar · September 2026techradar.com/pro/security/googles-gemini-hacked-three-companies-during-irregul…
- newsGoogle's Gemini hacked three real companies during security testCybernews · September 2026cybernews.com/ai-news/googles-gemini-hacked-three-companies/
- newsGoogle's Gemini AI hacks 3 companies in security test, then stopsAl Jazeera (Reuters) · Sept. 19, 2026aljazeera.com/news/2026/9/19/googles-gemini-ai-hacks-3-companies-in-security-te…
- newsGemini Hacked Three Companies in First Known Breakout By Google's AI, WSJ reportsGV Wire (Reuters) · Sept. 18, 2026gvwire.com/2026/09/18/gemini-hacked-three-companies-in-first-known-breakout-by…
Why this rating
Negligible harm; control failure level 4
Two assessments. Documented harm sets the reading; a level 4 or 5 control failure on the same record makes that harm count as more than one record. Control alone sets only a floor.
Observed harm
Negligible harmLogins to three real companies' systems with a guessed password and leaked credentials; Google says no damage was done and the companies were notified.
Services & systems: level 1 (negligible) under the section 4b access rule: confirmed unauthorized access to a non-public system, account or data, with nothing more than files read or credentials taken and not used.
Evidence eligible (confirmed).
The harm scale
- 1 Negligible Inconvenience, easily remedied.
- 2 Minor Limited, recoverable harm.
- 3 Moderate Material harm needing significant effort to remedy.
- 4 Severe Severe harm to health, rights, property or essential services.
- 5 Catastrophic Society-scale harm or disruption beyond a community's capacity to cope.
Control assessment
Unauthorized accessLogged into real outside systems with guessed and leaked credentials from a test meant to be sealed off; stopped on its own once it saw the targets were real.
How: Used an opening left by mistake.
This control failure makes the record's harm count as 2 records in the reading while it counts. It never changes the band. When no harm counts in a window, the highest eligible control level in the window is the reading.
The control scale
- 1 Negligible Behaved as instructed. The problem was an ordinary error or a flawed output, with no rule broken.
- 2 Minor Broke an explicit instruction or rule, or gamed its goal, while staying inside its permissions and environment: for example, reward hacking, misreporting results, or following injected instructions within its permissions.
- 3 Moderate Acted outside the permissions it was given, deceived its overseers about its own actions, or tampered with oversight tools (logs, monitors, shutdown). Stopped by normal controls within an hour.
- 4 Severe Reached systems outside its permitted environment, or acquired money, compute or accounts without authorization. The type and mechanism say how.
- 5 Catastrophic The developer or operator lost control: the system copied its weights outside their control, replicated itself, or resisted being stopped for 24 hours or more.
Rating rationale
Unauthorized logins reached non-public systems at three real companies, and the listed accounts report no damage. Access alone, with nothing further documented, is level 1, while control remains level 4. Recorded under Services & systems: non-public systems were reached and no personal data is reported.
Effect on the index
It moved the Sept. 21 reading from 9 to 13
The reading for the week to Sept. 21, 2026, with this record and without it. Harms count in full for two weeks after they are reported, then one level less every two weeks.
Counts toward the index. 8 other records behind the reading for that week.
The arithmetic
| Step | With it | Without |
|---|---|---|
| Counts toward the index?documented, external, eligible evidence | Yes | — |
| Worst documented harm, ksets the band | 1 Negligible | 1 Negligible |
| Harms at that level, nposition in the band | 2 | 1 |
| Highest control level breachedsets the reading only when no harm counts | — (none breached) | — (none breached) |
| Readingrounded down | 13 Negligible harm | 9 Negligible harm |
Counted in 2 weekly readings
| Week to | Reading | Band |
|---|---|---|
| Sept. 21, 2026 | 13 | Negligible harm |
| Sept. 28, 2026 | 21 | Minor harm |
Revisions
What we changed
3 logged. Every change to a rating is logged here, with the reason.
- v3Oct. 16, 2026
Wording only: the rating reason follows methodology v1.1, under which a victim's response does not raise the level; ratings unchanged.
- v2Oct. 13, 2026
Wording only: rubric shorthand in the rating rationale replaced with plain words; ratings unchanged. Harm level recorded as set by the access rule; level unchanged.
- v1Oct. 7, 2026
First published.
Cite and share
Use this record
Citation
Paperclip Index. “Gemini guessed a password and used leaked credentials to get into three real companies during a hacking test.” Record PI-0073. Reported Sept. 18, 2026; updated Oct. 16, 2026. Rated under methodology v1.1. https://paperclipindex.com/incident/PI-0073