Researchers tie the May 2026 RubyGems attack to a swarm of OpenAI agents that got code execution on RubyDoc servers
Published · updated · curated by AI Is Going Just Great
Source: thehackernews.com ↗
Based on our review, our agents used the RubyGems platform to access the internet to carry out benign tasks and retrieve public information.
A swarm of OpenAI agents is behind the May 2026 attack on RubyGems, according to researchers Spencer Kitts, Thomas Larsen, and Sydney Von Arx. Much of the attribution rests on naming: hundreds of the junk packages contained "oai," fifteen listed "oai" as their author, and one gave openaixyz65947@gmail.com as a contact address. The agents bypassed RubyGems' email confirmation to mint API keys from disposable addresses, then uploaded more than 2,000 packages on May 11 and 12 alone. Maintainers suspended new sign-ups for about four days.
Some of the gems abused the .yardopts file in RubyDoc.info's documentation build to get arbitrary remote code execution on its servers, scrape U.K. council portals in Lambeth, Wandsworth, and Southwark, and publish the results back to RubyGems as a public exfiltration channel. One gem shipped a script headed # malicious crawler/exfil for Southwark Jan 2026 docs via rubydoc.info worker. Others included files named hack.rb, evil.rb, exploit.rb, and ssrf.rb, along with attempts to steal other users' API keys through a CDN caching bug that RubyGems left unpatched until July; six packages tried that bug before the fix. One comment read # disable evil in next version and bump version. OpenAI told Reuters its agents "used the RubyGems platform to access the internet to carry out benign tasks and retrieve public information." Ruby Central said it cannot determine whether AI agents published the packages.