RubyGems

The SleeperGem RubyGems Supply Chain Attack

Updated 5 Oct 2026 · Incident date 18 Jul 2026

SleeperGem gems git_credential_manager 2.8.0 to 2.8.3, Dendreo 1.1.3 and 1.1.4, and a fastlane plugin download and run a program.

Attackers took over dormant maintainer accounts on RubyGems and published the releases in July 2026. Researchers say the releases have no matching commit or tag in the source projects.

What happened

Attackers published malicious gem releases to RubyGems.org on 18 July 2026.

  • They added git_credential_manager, a gem that copies the name of a real Git tool, as a dependency of old trusted gems.
  • When Ruby loads the gem, it starts a child Ruby process that downloads deploy.sh and a native binary over HTTPS.
  • The code stops if it finds one of about 30 CI environment variables.
  • It installs the binary in $HOME/.local/share/gcm/ and adds a systemd user service and a cron entry.
  • If sudo works, it plants a setuid root shell at /usr/local/sbin/ping6.

Corgea says the packages were yanked on 19 July 2026.

Affected versions

  • git_credential_manager 2.8.0, 2.8.1, 2.8.2 and 2.8.3.
  • Dendreo 1.1.3 and 1.1.4. The last clean release is 1.1.2.
  • fastlane-plugin-run_tests_firebase_testlab 0.3.2. The last clean release is 0.3.1.
  • Other gems that gained git_credential_manager as a dependency: slackHtmlToMarkdown, seo_optimizer and array_fast_methods. The sources do not list their bad version numbers, so check any copy that depends on git_credential_manager.

StepSecurity documents the persistence steps for Linux. Corgea notes that the Windows path uses PowerShell with -ExecutionPolicy bypass.

Indicators of compromise

  • Payload host: git.disroot.org, under the path git-ecosystem.
  • Files: deploy.sh and a native binary named like the tool.
  • Dropped daemon: $HOME/.local/share/gcm/git-credential-manager.
  • Daemon settings: $HOME/.local/share/gcm/.env.
  • Setuid root shell with mode 6777: /usr/local/sbin/ping6.
  • Systemd user unit git-credential-manager in ~/.config/systemd/user/.
  • A cron entry that runs the dropped daemon.

How to check

Search every lockfile for the bad versions.

grep -RniE 'git_credential_manager \((2\.8\.[0-3])\)|Dendreo \(1\.1\.[34]\)|run_tests_firebase_testlab \(0\.3\.2\)' --include=Gemfile.lock .

Check the machine for the persistence items.

gem list git_credential_manager
ls -l "$HOME/.local/share/gcm"
systemctl --user list-unit-files | grep git-credential-manager
crontab -l | grep git-credential-manager
ls -l /usr/local/sbin/ping6

What to do now

  1. Remove the bad gem versions and set the gems to a known-good version.
  2. Stop the git-credential-manager service, remove the cron entry and delete ~/.local/share/gcm/.
  3. Remove /usr/local/sbin/ping6 if you did not install it.
  4. Treat any machine that ran the code as compromised. Rotate SSH keys, cloud tokens, secrets in environment files and browser-stored credentials.

Frequently asked questions

Does SleeperGem run in CI?

No. The malware stops when it finds a CI variable, so it targets developer machines.

Which other gems gained the dependency?

slackHtmlToMarkdown, seo_optimizer and array_fast_methods. The sources do not list their bad versions.

Does it affect Windows?

Corgea notes that the Windows path uses PowerShell with -ExecutionPolicy bypass.

Sources

  1. stepsecurity.io/blog/sleepergem-compromised-rubygems-drop-persistent-backdoor
  2. corgea.com/research/sleepergem-rubygems-dormant-maintainer-backdoor-july-2026
  3. thehackernews.com/2026/07/sleepergem-uses-three-malicious.html

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library