Export
The link always opens the latest version of this page.
Ask an AI about it
Open in ChatGPTA new chat that reads this entry from the site Open in ClaudeThe same, in ClaudeShare the link instead of a file, and they will always see the latest version.
Files are a snapshot of today. The live page has anything newer.
RubyGems malicious package upload incident
A security incident in which malicious packages were uploaded to the rubygems registry, attributed to OpenAI 1.
The attackers exploited this access to distribute malicious gems through the official package repository.
This resurgence demonstrated that the initial remediation efforts had not fully eliminated the attackers' persistence mechanisms or access vectors.
The incident affected the integrity of the RubyGems supply chain, as legitimate developers could inadvertently install compromised packages. The compromise of API keys created additional risk for package maintainers whose credentials were exposed.
Facts 3
| Attribute | Value | Confidence | Sources | Cited |
|---|---|---|---|---|
| Date | 2026-05-11 | low | 1 | 1 |
| Victim | RubyGems registry, RubyDoc.info, API key holders | low | 1 | 1 |
| Impact | 2000+ malicious packages uploaded; RubyGems disabled new user registration for four days
also reported: Agents uploaded 700+ malicious packages to public registry in May 2026 (low)
|
low | 1 | 1 |
Neighbourhood
Targets 2
Frequently mentioned together 2
Sources 2
- OpenAI's malicious bot swarm attacked RubyGems · The Register: Security
- If We're Calling It Superintelligence, We Have to Build It Carefully · HackerNoon