<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[RubyGems Suspends New Signups Following Mass Malicious Package Injection]]></title><description><![CDATA[<p>RubyGems Suspends New Signups Following Mass Malicious Package Injection</p><p>RubyGems suspended new account registrations after attackers uploaded hundreds of malicious packages containing exploits to the repository.</p><p>**If you're a Ruby developer, audit your Gemfile.lock for any unfamiliar or recently added dependencies and run bundle-audit to scan for known vulnerabilities. Avoid installing or updating gems until RubyGems confirms the cleanup is complete, and treat any new dependency added in the last few days with extra suspicion.**<br /><a href="https://infosec.exchange/tags/cybersecurity" rel="tag">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/infosec" rel="tag">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/incident" rel="tag">#<span>incident</span></a> <a href="https://infosec.exchange/tags/ransomware" rel="tag">#<span>ransomware</span></a><br /><a href="https://beyondmachines.net/event_details/rubygems-suspends-new-signups-following-mass-malicious-package-injection-x-e-f-z-2/gD2P6Ple2L" rel="nofollow noopener"><span>https://</span><span>beyondmachines.net/event_detai</span><span>ls/rubygems-suspends-new-signups-following-mass-malicious-package-injection-x-e-f-z-2/gD2P6Ple2L</span></a></p>]]></description><link>https://board.circlewithadot.net/topic/12a3886d-7c35-454c-9794-f22127d17be3/rubygems-suspends-new-signups-following-mass-malicious-package-injection</link><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 10:26:34 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/12a3886d-7c35-454c-9794-f22127d17be3.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 13 May 2026 10:01:07 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to RubyGems Suspends New Signups Following Mass Malicious Package Injection on Wed, 13 May 2026 14:13:03 GMT]]></title><description><![CDATA[<p><span><a href="https://mas.to/@jschwart">@<span>jschwart</span></a></span> no reports on gem.coop. <br />RubyGems were quite loud about this, and we can't find whether gem.coop uses the same  files published to RubyGems...</p><p>Safest approach is to still do the same level of review as if gem.coop was attacked.</p>]]></description><link>https://board.circlewithadot.net/post/https://infosec.exchange/users/beyondmachines1/statuses/116567676249226616</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://infosec.exchange/users/beyondmachines1/statuses/116567676249226616</guid><dc:creator><![CDATA[beyondmachines1@infosec.exchange]]></dc:creator><pubDate>Wed, 13 May 2026 14:13:03 GMT</pubDate></item><item><title><![CDATA[Reply to RubyGems Suspends New Signups Following Mass Malicious Package Injection on Wed, 13 May 2026 10:04:01 GMT]]></title><description><![CDATA[<p><span><a href="/user/beyondmachines1%40infosec.exchange">@<span>beyondmachines1</span></a></span> does this apply only if you missed switching over to gem.coop or is that affected as well?</p>]]></description><link>https://board.circlewithadot.net/post/https://mas.to/users/jschwart/statuses/116566697046405421</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mas.to/users/jschwart/statuses/116566697046405421</guid><dc:creator><![CDATA[jschwart@mas.to]]></dc:creator><pubDate>Wed, 13 May 2026 10:04:01 GMT</pubDate></item></channel></rss>