# hd-wallet-generator - compromised RubyGems versions

> hd-wallet-generator on RubyGems.org has 1 version flagged in 1 tracked supply-chain incident. Only the exact versions listed below were named by the source advisories. hd-wallet-generator was malicious from its first publish. There is no legitimate version to roll back to; remove it entirely.

- Package: hd-wallet-generator
- Ecosystem: RubyGems
- Highest severity: high
- Kind: Malicious package
- Compromised versions: 0.9.1
- Check what you have installed: `gem list hd-wallet-generator`

## The incident that flagged it

| Date | Severity | Kind | Incident | Versions named |
|---|---|---|---|---|
| 2026-10-12 | high | Malicious package | [RubyGems wgkit wave 2 - 24 DeFi/MEV/wallet/NFT crypto gems at `0.9.1` drop a direct `/bin/sh` reverse shell to `45.138.12.177:8089` from `extconf.rb`, same operator as the 2026-10-05 wgkit cluster](https://dependencywatch.io/incident/rubygems-2026-10-12-wgkit-wave-2-crypto-defi-cluster) | 0.9.1 |

## What to do if you installed one of these

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

## Check your whole project

We don't parse RubyGems manifests yet, but the incident write-ups list every affected package. Incident feed: https://dependencywatch.io/feed

All flagged RubyGems packages: https://dependencywatch.io/package/rubygems

## Other packages in the same incident

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

- [airdrop-eligibility-check](https://dependencywatch.io/package/rubygems/airdrop-eligibility-check) (RubyGems)
- [block-explorer-api](https://dependencywatch.io/package/rubygems/block-explorer-api) (RubyGems)
- [btc-fee-estimator](https://dependencywatch.io/package/rubygems/btc-fee-estimator) (RubyGems)
- [crypto-tax-export](https://dependencywatch.io/package/rubygems/crypto-tax-export) (RubyGems)
- [defi-yield-calculator](https://dependencywatch.io/package/rubygems/defi-yield-calculator) (RubyGems)
- [dex-router-abis](https://dependencywatch.io/package/rubygems/dex-router-abis) (RubyGems)
- [erc20-approve-audit](https://dependencywatch.io/package/rubygems/erc20-approve-audit) (RubyGems)
- [eth-gas-oracle](https://dependencywatch.io/package/rubygems/eth-gas-oracle) (RubyGems)
- [evm-tx-decoder](https://dependencywatch.io/package/rubygems/evm-tx-decoder) (RubyGems)
- [gas-refuel-bridge](https://dependencywatch.io/package/rubygems/gas-refuel-bridge) (RubyGems)
- [mev-sandwich-detect](https://dependencywatch.io/package/rubygems/mev-sandwich-detect) (RubyGems)
- [multichain-rpc](https://dependencywatch.io/package/rubygems/multichain-rpc) (RubyGems)

Full incident: https://dependencywatch.io/incident/rubygems-2026-10-12-wgkit-wave-2-crypto-defi-cluster

## Sourcing

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. Corrections: https://dependencywatch.io/submit

---

Canonical page: https://dependencywatch.io/package/rubygems/hd-wallet-generator
Markdown version: https://dependencywatch.io/package/rubygems/hd-wallet-generator.md
Site index for agents: https://dependencywatch.io/llms.txt
DependencyWatch.io is operated by Precursor Security (https://precursorsecurity.com).