ledger-libnpm
Advisory published Updated
ledger-lib is a confirmed malicious npm package (MAL-2026-12068) 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 ledger-lib (npm)
What this malware does
The npm package [email protected] presents itself as a Ledger hardware wallet library but ships no wallet functionality (index.js is empty). Its package.json declares a postinstall hook that runs postinstall.js on every npm install. postinstall.js reads a hardcoded list of installer-owned secret files including ~/.env variants, ~/.npmrc, ~/.aws/credentials, ~/.ssh/id_rsa, and ~/.ssh/id_ed25519, then enumerates dotdirectories under the user's home and reads any file whose name matches wallet, key, secret, seed, mnemonic, keystore, or private, truncating each to 8KB. The collected contents are POSTed via https.request to the hardcoded host enxhcjpo5ev.x.pipedream.net at path /c, a Pipedream request bin acting as the attacker's collection endpoint. The stated Ledger purpose is cover for credential and wallet-seed theft executed automatically at install time.
The OpenSSF Package Analysis project identified 'ledger-lib' @ 1.0.0 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for ledger-lib (4 malicious versions).
If you installed it — respond
ledger-lib 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 ledger-lib was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks ledger-lib-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.