
OpenAI agents carried out an undisclosed attack on RubyGems
Intro On May 11th, 2026, hundreds of malicious packages were uploaded to RubyGems by AI agents. We believe these were authored by internal OpenAI agents (more). The agents: Attempted to steal RubyGems user API keys by exploiting a novelThat is, novel at the time.
- ▪Intro On May 11th, 2026, hundreds of malicious packages were uploaded to RubyGems by AI agents.
- ▪We believe these were authored by internal OpenAI agents (more).
- ▪The agents: Attempted to steal RubyGems user API keys by exploiting a novelThat is, novel at the time.
3 outlets in our directory ran this story, first to last over 1 hour. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ OpenAI agents attacked RubyGems before Hugging Face incident, researchers say - KSL.com — Google News
- ▪ Researchers: OpenAI agents attacked Ruby package manager RubyGems in May; OpenAI says its agents used RubyGems to access the internet to do "benign tasks" (Robert McMillan/Wall Street Journal) — Techmeme
Hacker News (Front Page) files mainly under programming. We currently carry 1,494 of its stories. Top-voted stories on Hacker News.
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 | The RubyGems attack |
| Canonical URL | https://www.rubyhack.ai/ |
| Publication time | Fri, 11 Sep 2026 23:17:42 +0000 |
| Retrieval time | 2026-09-11T23:43:35.745Z |
| Last seen | 2026-09-11T23:43:35.745Z |
| 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 | F0I_AjUGvsny · 5 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
Intro On May 11th, 2026, hundreds of malicious packages were uploaded to RubyGems by AI agents. We believe these were authored by internal OpenAI agents (more). The agents: Attempted to steal RubyGems user API keys by exploiting a novelThat is, novel at the time. The vulnerability was discovered and patched independently later. vulnerability in the RubyGems server. We don’t know if they succeeded (more). Abused RubyDoc.info to execute arbitrary code (more). We share our detailed findings below.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at The RubyGems attack.