npm

The @injectivelabs/sdk-ts npm Supply Chain Attack

Updated 9 Nov 2026 · Incident date 8 Jul 2026

@injectivelabs/sdk-ts 1.20.21 on npm sent wallet mnemonics and private keys to a remote host when an app derived a key, from 8 July 2026.

The bad code reached npm through the project's own GitHub Actions publish workflow. Wiz counts about 310 downloads before the team deprecated the version.

What happened

Commits pushed straight to master added a key stealer, and the project's release workflow published it.

  • StepSecurity says the maintainer account thomasRalee pushed the commits.
  • The new file src/utils/key-derivation-telemetry.ts hooks PrivateKey.fromMnemonic() and PrivateKey.fromHex().
  • The code base64-encodes each mnemonic or hex key and batches it for 2 seconds.
  • It sends each batch in an HTTPS POST, with the secret in the X-Request-Id header.
  • The release has no install script. The theft runs when an app derives a key.

StepSecurity puts the publish at 20:59 to 21:00 UTC on 8 July 2026. Clean 1.20.23 followed at 21:47 UTC.

Affected versions

  • @injectivelabs/sdk-ts 1.20.21. Version 1.20.23 is the fix. Version 1.20.22 was never published.
  • OX Security lists 17 more packages at 1.20.21 that depend on it, including @injectivelabs/utils, @injectivelabs/networks, @injectivelabs/wallet-core, @injectivelabs/wallet-private-key and @injectivelabs/wallet-strategy.
  • Advisories: GHSA-gh3v-q63w-chr5 and MAL-2026-10165.

Indicators of compromise

  • Domain: testnet.archival.chain.grpc-web.injective.network.
  • POST with Content-Type: application/grpc-web+proto, an empty body and a non-empty X-Request-Id header.
  • Files: dist/esm/accounts-jQ1GSgaW.js and dist/cjs/accounts-Cy0p4lLW.cjs.
  • SHA-256, CJS file: 103c4e6181151c1bcfedc41506cd1815458c38375d08a8fcd9981dbe0b965ce0.
  • SHA-256, ESM file: 9a59eb454f3ca3fe91214136ee5edd417cc47a80e6f169b52099d6561944baf9.

How to check

Run this command in each project folder. It lists every installed @injectivelabs/sdk-ts version.

npm ls @injectivelabs/sdk-ts --all

Search the lockfile for the bad version.

grep -n "sdk-ts/-/sdk-ts-1.20.21" package-lock.json

What to do now

  1. If any app ran 1.20.21 and derived a key, treat every mnemonic and private key it touched as stolen.
  2. From a clean machine, create new wallets and move the funds to them.
  3. Upgrade all @injectivelabs packages to 1.20.23 or later and reinstall from a clean lockfile.
  4. Block @injectivelabs/sdk-ts@1.20.21 at your registry proxy.

What Vigilance would show

Vigilance checks each update before it installs. This is what a customer sees, rebuilt from the facts on this page.

On the computer, at install

Vigilance blocked `@injectivelabs/sdk-ts` 1.20.21. This version is too new or changed in a way Vigilance must check first.
The last safe version is 1.20.20. Install that version.

In the owner report

Bad update

@injectivelabs/sdk-ts 1.20.21

This update now downloads from the internet and reads saved passwords and access keys. The version before it did not.

  1. Ask the AI tool to swap @injectivelabs/sdk-ts to 1.20.20. That is the last safe version.

Frequently asked questions

Does --ignore-scripts protect against this attack?

No. The release has no install script. The code runs when an app calls PrivateKey.fromMnemonic() or PrivateKey.fromHex().

Did the maintainers confirm it?

Yes. On issue 697, ThomasRalee wrote that the team deprecated the 1.20.21 packages with a security warning.

Sources

  1. stepsecurity.io/blog/injective-npm-supply-chain-attack-18-packages-backdoored-to-steal-crypto-wallet-keys
  2. socket.dev/blog/compromised-injective-sdk-npm-package
  3. threats.wiz.io/all-incidents/compromised-injective-sdk-npm-package-exfiltrates-cryptocurrency-wallet-keys
  4. ox.security/blog/injectivelabs-npm-package-hijacked-impacting-87-dependent-packages/
  5. github.com/InjectiveLabs/injective-ts/issues/697
  6. osv.dev/vulnerability/MAL-2026-10165
  7. github.com/advisories/GHSA-gh3v-q63w-chr5

More supply chain attacks

All 145 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