If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (440db517e7261bf345aa374ab2afb8d91698929115a8d3d67abd9fbf7018362e)
The npm package ledger-lib@1.0.0 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.
Source: ossf-package-analysis (5b623fc6d2442970b8576d251252a68520b6b027d42fd9357051f8405769cc9d)
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.