npm

The Ledger Connect Kit Supply Chain Attack

Updated 5 Oct 2026 · Incident date 14 Dec 2023

@ledgerhq/connect-kit 1.1.5, 1.1.6 and 1.1.7 on npm carried a wallet drainer that tricked visitors into approving transfers, for about five hours on 14 December 2023.

The attacker phished the npm account of a former Ledger employee. Version 1.1.8 is the fixed release.

What happened

The attacker published three poisoned versions of @ledgerhq/connect-kit to npm.

  • The code tricked users into sending funds to the attacker through a rogue WalletConnect project.
  • The package powers wallet connections for apps such as SushiSwap and Revoke.cash.
  • Most funds left victim wallets in under two hours.
  • Checkmarx reports that more than $700,000 was stolen.
  • The poisoned versions had no matching Git tags or releases in the source repository.

The code was live for about five hours on 14 December 2023. Ledger released the fix within 40 minutes of the alert.

Affected versions

  • @ledgerhq/connect-kit 1.1.5 (malicious).
  • @ledgerhq/connect-kit 1.1.6 (malicious).
  • @ledgerhq/connect-kit 1.1.7 (malicious).
  • @ledgerhq/connect-kit 1.1.8 (fixed).
  • 1.1.4 and earlier are the releases before the attack.

Indicators of compromise

  • @ledgerhq/connect-kit at version 1.1.5, 1.1.6, or 1.1.7 in package-lock.json, yarn.lock, or node_modules.
  • An npm release with no matching Git tag or release in the source repository.
  • Wallet approval requests that route funds through an unknown WalletConnect project.

How to check

List the installed version. The command does not run the package.

npm ls @ledgerhq/connect-kit

Search lock files in every repository and build output.

grep -rn -A1 '@ledgerhq/connect-kit' package-lock.json yarn.lock pnpm-lock.yaml

What to do now

  1. Upgrade @ledgerhq/connect-kit to 1.1.8 or later. Then rebuild and redeploy every site that bundles it.
  2. If a site ran an affected version on 14 December 2023, tell your users to review their wallets.
  3. Rotate npm and GitHub publishing credentials. Turn on two-factor authentication for each account that can publish.
  4. Compare each new npm release with a Git tag before you trust it.

What Vigilance would show

These examples show an install hold and the corresponding owner report.

Example install message

Vigilance blocked `@ledgerhq/connect-kit` 1.1.5. This version is too new or changed in a way Vigilance must check first.

Example owner report

Bad update

@ledgerhq/connect-kit 1.1.5

A wallet-connection widget gained code that tricked visitors into approving transfers that emptied their cryptocurrency accounts.

See what to do now.

No security team? See who reads the alert.

Frequently asked questions

What did Ledger change afterwards?

Ledger rotated its GitHub publishing secrets and set npm project permissions to read-only. WalletConnect turned off the rogue project.

Is the rogue project ID known?

Socket and Checkmarx do not publish the project ID or the attacker wallet address.

Sources

  1. socket.dev/blog/ledger-connect-kit-supply-chain-attack-wallet-drainer
  2. checkmarx.com/blog/npm-account-takeover-results-in-crypto-supply-chain-attack/

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 · npm supply chain attacks · 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