SleeperGem supply chain attack: three malicious Ruby packages with staged payload delivery
Three trojanised RubyGems packages were published to RubyGems.org with names mimicking legitimate tools, designed to download and execute additional payloads on developer machines. This represents an active supply chain compromise targeting the Ruby ecosystem.
Affected
SleeperGem represents a deliberate supply chain attack exploiting the Ruby ecosystem's trust model. The attacker published multiple versions of malicious gems to RubyGems.org, including git_credential_manager (versions 2.8.0 through 2.8.3, published 18 July 2026) and Dendreo (versions 1.1.3 and 1.1.4), chosen to create confusion with legitimate tools and encourage installation through dependency resolution or typosquatting.
The staged payload architecture is the key technical detail here. Rather than embedding the final malicious functionality directly, these gems fetch and execute secondary payloads after installation. This approach provides several advantages to the attacker: it evades static analysis of the package contents, allows flexible targeting based on infection timing, and complicates incident response by separating initial compromise from actual exploitation. Developers who installed these versions between 18 July and discovery would have opened an arbitrary code execution vector on their machines.
The scope of exposure depends on installation patterns. If any of these gems landed in popular projects or were pulled as transitive dependencies, the blast radius could extend well beyond direct installations. Ruby's gem ecosystem has seen similar attacks before, but the use of credential-manager-adjacent naming suggests this campaign targets development infrastructure with access to source repositories or deployment systems.
Defenders should immediately audit Gemfile.lock files and CI/CD logs for these package names and versions. Organisations should rotate any credentials that may have been exposed on affected developer machines. The Ruby community and RubyGems.org administrators should review acceptance criteria for new packages, including homoglyph detection and name confusion prevention, given the ease with which legitimate-sounding names bypass initial scrutiny.
This incident reinforces that package repository security remains fundamentally reactive. No amount of code review catches malicious gems already in the repository, and discovery typically occurs weeks or months after publication. The staged delivery pattern will likely become more common as attackers seek to avoid honeypots and automated scanning.
Sources