HighRubyGems4 affected versions

git_credential_manager

git_credential_manager has 4 versions on RubyGems.org flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with gem list git_credential_manager.

  • git_credential_manager@2.8.3
  • git_credential_manager@2.8.2
  • git_credential_manager@2.8.1
  • git_credential_manager@2.8.0

The incident that flagged it

High

SleeperGem - dormant RubyGems maintainer takeover drops persistent developer-laptop backdoor via `git.disroot.org` Forgejo second-stage (git_credential_manager, Dendreo, fastlane-plugin-run_tests_firebase_testlab)

On 2026-07-18 → 07-19 an actor reactivated two long-dormant RubyGems maintainer accounts (Dendreo, dormant since 2020; fastlane-plugin-run_tests_firebase_testlab, dormant since 2019) and published a brand-new git_credential_manager gem impersonating Microsoft's Git Credential Manager. Seven malicious releases across three gems fetch a second-stage binary from git.disroot.org/git-ecosystem/* (Forgejo), skip execution if any of ~30 CI env vars are present, and drop a persistent native daemon on developer laptops.

Versions named here: 2.8.0, 2.8.1, 2.8.2, 2.8.3

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

  1. 1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
  2. 2.Pin to a version not listed above, then reinstall from a clean lockfile.
  3. 3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
  4. 4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

git_credential_manager is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. We don't parse RubyGems manifests yet, but the incident write-ups list every affected package.

Other packages in the same incident

If git_credential_manager is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.