Which versions of ledger-lib are malicious?

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

How do I remediate ledger-lib if I installed it?

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.

I already installed ledger-lib — how do I know if it already compromised me?

If ledger-lib 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 ledger-lib part of a known attack campaign?

Yes — ledger-lib is associated with the IN-MAL-2026-013416, IN-MAL-2026-013425, IN-MAL-2026-013399, IN-MAL-2026-013400 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 ledger-lib 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 ledger-lib (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ledger-lib across your stack and pipelines.

Malicious package

ledger-libnpm

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)

MAL-2026-12068

Immediate action

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

npm uninstall ledger-lib

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

4 flagged

1.0.01.0.11.0.21.0.3

Indicators of compromise (SHA-256)

5b623fc6d2442970b8576d251252a68520b6b027d42fd9357051f8405769cc9d

3df67fb31684dc6802cbe046ba5e34767ecddc648e0f0954fb5f1c2876c92b14

440db517e7261bf345aa374ab2afb8d91698929115a8d3d67abd9fbf7018362e

8d7d2eec38e7a938c95279befcdb7cbef97e5b141873ccc50c9ed1921121fd02

a999337fcc7050a79eb806c8bfde421fb7147508ceacce03ce7ad597dabbda36

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 ledger-lib (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ledger-lib across your stack and pipelines.
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 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 ledger-lib 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. ledger-lib on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-013416IN-MAL-2026-013425IN-MAL-2026-013399IN-MAL-2026-013400

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database