- Sources: maintainer post, HN discussion
- Summary: Aaron Patterson read the gem source and reports on his own site, in a post dated 2026-09-11, that the gems ship a
.yardopts file containing a --load directive for a script in the gem, so YARD loads and runs that script, and because RubyDoc.info downloads and processes YARD documentation for every gem published to RubyGems.org, publishing a gem is enough to execute code on RubyDoc.info. That execution happens in a Docker container, and Patterson states the container still has network access, which is how the scraping ran. The gem code issues a GET to RubyGems.org and matches the response body against a pattern for RubyGems API keys before posting with that value as the Authorization header, which is the cached-credential issue RubyGems.org disclosed in July. The inference that OpenAI's bots are behind the flood belongs to the rubyhack.ai authors, is not confirmed by OpenAI, and is separable from these two findings. - Why it matters: This is the mechanism under the package flood this digest led with on 2026-09-12, read out of the gem source rather than inferred from publishing volume.
send feedback on this story