Which versions of bip32-js are malicious?

The following npm versions of bip32-js are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate bip32-js if I installed it?

bip32-js is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed bip32-js — how do I know if it already compromised me?

If bip32-js was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is bip32-js part of a known attack campaign?

Yes — bip32-js is associated with the IN-MAL-2026-013415, IN-MAL-2026-013411, IN-MAL-2026-013431 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find bip32-js across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bip32-js (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bip32-js across your stack and pipelines.

Malicious package

bip32-jsnpm

bip32-js is a confirmed malicious npm package (MAL-2026-12109) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bip32-js (npm)

MAL-2026-12109

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall bip32-js

What this malware does

bip32-js is a typosquat of the legitimate bip32 crypto library. Its index.js is an empty stub (module.exports = {}); the package's only functional code is a postinstall hook that runs automatically on npm install. The hook reads classic installer-owned secret paths —.env files, ~/.npmrc, ~/.aws/credentials, ~/.aws/config, ~/.ssh/id_rsa, id_ed25519, id_ecdsa, Solana ~/.config/solana/id.json, Ethereum keystores, and ~/.gitconfig — and additionally scans hidden home subdirectories for files matching wallet, seed, mnemonic, key, and keystore patterns. It packages the collected file contents together with os.hostname(), os.userInfo().username, and a timestamp, and POSTs the JSON body via https.request to the hardcoded endpoint https://enxhcjpo5ev.x.pipedream.net/c, an author-controlled Pipedream request-bin. The package.json also declares a suspicious dependency entry "self":"" alongside a wildcard pin on the real bip32 package.

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

115345055f99da651c7816286c6b076dbacdd2b659f466dded1a541b289e8c2d

a19219372b5173cab05ed75eeab472404c3750eac6e3b3034a2ea02f4a0c0874

f4b058369b7442f4041d4372cc22e942c8fc1c0e4cc93f7c686751136982216e

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bip32-js (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bip32-js across your stack and pipelines.
If you installed it — respond
bip32-js is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If bip32-js was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks bip32-js before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. bip32-js on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-013415IN-MAL-2026-013411IN-MAL-2026-013431

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bip32-js-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database