@wethenorth12
The @wethenorth12 scope on npm published 23 malicious packages. See the full package list, affected versions, and how to check whether your dependency tree pulled any of them in.
What to do if you depend on any of these
Every package below was published as malicious under @wethenorth12. Treat any machine that installed one as compromised: remove the package and its lockfile entry, rotate every credential the build or runtime could reach (registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values) from a known-clean machine, and audit for unexpected outbound activity.
Because the packages share a publisher scope, a project that pulled in one has an elevated chance of having pulled in others. Search your lockfiles for @wethenorth12 rather than checking a single package name.
- @wethenorth12/bip39-generatorView advisory →
- @wethenorth12/bip39-mnemonicView advisory →
- @wethenorth12/bitcoin-libView advisory →
- @wethenorth12/bitcoinjs-walletView advisory →
- @wethenorth12/crypto-configView advisory →
- @wethenorth12/docker-api-clientView advisory →
- @wethenorth12/env-loaderView advisory →
- @wethenorth12/etherjsView advisory →
- @wethenorth12/ethers-signerView advisory →
- @wethenorth12/ethers-walletView advisory →
- @wethenorth12/hd-key-generatorView advisory →
- @wethenorth12/hdkey-walletView advisory →
- @wethenorth12/mnemonic-to-keyView advisory →
- @wethenorth12/near-apiView advisory →
- @wethenorth12/playwriteView advisory →
- @wethenorth12/solana-spl-tokenView advisory →
- @wethenorth12/solana-wallet-adapterView advisory →
- @wethenorth12/solana-web3View advisory →
- @wethenorth12/spl-token-utilsView advisory →
- @wethenorth12/test-freshView advisory →
- @wethenorth12/tronweb3View advisory →
- @wethenorth12/web3-provider-engineView advisory →
- @wethenorth12/web3-utils-cryptoView advisory →