
Four AI lab breaches were caused by a single underlying issue, Irregular says
Google CEO Sundar Pichai at the World Economic Forum Credit: WEF/Greg Beadle Google has confirmed that its Gemini model inadvertently broke into three company systems in May during cybersecurity testing. Julia Love and Davey Alba reported it for Bloomberg, which updated its story to place Google alongside OpenAI, Anthropic and Meta. The important part is what the testing vendor said next.
- ▪Google CEO Sundar Pichai at the World Economic Forum Credit: WEF/Greg Beadle Google has confirmed that its Gemini model inadvertently broke into three company systems in May during cybersecurity testing.
- ▪Julia Love and Davey Alba reported it for Bloomberg, which updated its story to place Google alongside OpenAI, Anthropic and Meta.
- ▪The important part is what the testing vendor said next.
Hacker News (AI / LLM) files mainly under ai. We currently carry 5,615 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | TNW | Security |
| Canonical URL | https://thenextweb.com/news/irregular-four-labs-one-issue-disclosure-timeline-gemini |
| Publication time | Sat, 19 Sep 2026 15:43:32 +0000 |
| Retrieval time | 2026-09-19T15:48:46.525Z |
| Last seen | 2026-09-19T15:48:46.525Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | N5Xkh9uMEct5 · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Google CEO Sundar Pichai at the World Economic Forum Credit: WEF/Greg Beadle Google has confirmed that its Gemini model inadvertently broke into three company systems in May during cybersecurity testing. Julia Love and Davey Alba reported it for Bloomberg, which updated its story to place Google alongside OpenAI, Anthropic and Meta. The important part is what the testing vendor said next. Irregular confirmed that the breaches disclosed by all four companies were part of the same issue, and that it told the relevant developers in late July. One incident, four announcements This has been reported for months as a string of separate breakouts by different models at different companies. TNW reported in August that a single testing vendor sat behind the OpenAI, Anthropic and Meta incidents.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at TNW | Security.