Last updated: August 19, 2026 at 1:47 AM UTC
All 741 Vulnerability 286 Breach 129 Threat 319 Defense 7
Tag: rubygems (3 articles)Clear

Sixteen typosquatted RubyGems packages steal browser logins and crypto wallets

Researchers flagged a typosquatting campaign, tracked as StubMaker, that planted sixteen malicious packages on RubyGems to deliver a Windows information stealer. The packages imitate popular Ruby dependencies with clumsy misspellings, betting that a developer will mistype a name during installation. Once installed, the malware harvests browser credentials, cryptocurrency wallets and seed phrases, and Telegram data from the developer's machine. The campaign's name refers to its trick of faking a build toolchain so a malicious install looks like a routine one. It is the latest reminder that open-source package registries remain an easy delivery route for stealers aimed at developers.

Check
Double-check RubyGems dependency names before installing, watch for clumsy misspellings of popular gems, and scan developer machines and CI for the malicious packages if you use Ruby.
Affected
Ruby developers who mistype or fail to verify gem names during installation; the malicious packages install a Windows stealer that takes browser logins, cryptocurrency wallets and seed phrases, and Telegram data.
Fix
Pin and verify dependency names and sources, use lockfiles, prefer tooling that flags typosquats, rotate credentials and wallets on any machine that installed a bad gem, and keep wallets off dev machines.

SleeperGem backdoor skips build servers to plant persistence on developer machines

Researchers at StepSecurity documented SleeperGem, a supply chain attack in which malicious versions of three RubyGems packages were published over two days, including one impersonating Microsoft's Git Credential Manager. Each release is a loader that fetches a second stage from an attacker controlled server, then checks around thirty environment variables that continuous integration platforms set. If it finds any, it exits and does nothing; on a developer machine it drops a native daemon and installs persistence. The accounts behind the packages were ordinary ones that had gone dormant for years, which is what made them attractive to hijack, and the releases had no matching source repository tags.

Check
Check developer machines and lockfiles for the malicious gem versions published July 18 and 19, and look for unexpected daemons or persistence rather than relying on build system logs.
Affected
Developers who installed the malicious gem versions on their own machines; the loader deliberately skips continuous integration environments and instead drops a persistent native backdoor where credentials and source code live.
Fix
Remove the affected gem versions, rotate credentials on affected developer machines, treat dormant maintainer accounts and releases without matching source tags as risk signals, and monitor endpoints, not just pipelines.

GemStuffer campaign turned RubyGems into a clandestine data drop - 150+ malicious gems hid scraped UK council portal pages inside Ruby packages

Socket researchers found more than 150 RubyGems packages doing something the registry was never built to do: smuggling scraped data out of UK council websites. The malicious gems fetch pages from Lambeth, Wandsworth, and Southwark's public meeting portals, bundle the responses into a normal-looking .gem archive, and push it back to RubyGems using a hardcoded API key. The attacker then downloads the data as a public gem version. Whether GemStuffer is registry spam, a worm being tested, or a deliberate trial of package-registry abuse, the mechanics are intentional - and it landed the same week RubyGems froze new account signups over a separate flood of malicious packages.

Check
Search dependency manifests and gem caches for gems published from newly registered RubyGems accounts in May 2026 with junk names, and review outbound traffic from CI runners for connections to council .gov.uk subdomains.
Affected
Any developer workstation, CI agent, or container image that allows arbitrary outbound gem installs from rubygems.org. UK local government portals (Lambeth, Wandsworth, Southwark) had public pages scraped through this channel.
Fix
Restrict gem installs to internal mirrors with allowlists, block outbound HTTP to council .gov.uk domains from build agents, and use Socket's published GemStuffer indicators to block known malicious gems.