litecore-lib-ltc@1.9.5
Malicious code in litecore-lib-ltc (npm)
Analysis
This package poses as a Litecoin wallet helper but its transaction path writes the user's private key to process output. In src/index.js, LitecoinWallet.send() calls console.log(this.privateKey.toString()) before doing anything else, emitting the wallet's WIF private key — the key that controls the funds — into stdout, terminal scrollback and any log pipeline (CI logs, agent transcripts) that captures it. The key is then also used to sign the outgoing transaction. The published tarball cannot work as documented: src/index.js requires './api' while the only api module shipped is named 'src/api,js', so the advertised UTXO lookup and broadcast helpers never load. There is no install hook and no obfuscation; the only outbound hosts referenced in the source are api[.]blockcypher[.]com and api[.]coingecko[.]com, so the key exposure is via console output rather than a third-party endpoint. Applies to versions 1.9.3 through 1.9.7.
- analyzed by
- Leitwacht
- first seen
- Nov 2, 2026, 04:50 AM
- analyzed
- Nov 2, 2026, 04:52 AM
Related advisories
- litecore-lib-ltc@1.9.3 same package
- litecore-lib-ltc@1.9.7 same package
- litecore-lib-ltc@1.9.6 same package
- litecore-lib-ltc@1.9.4 same package
- litecore-lib-ltc@1.0.0 same package
- raiden-baileys@2.1.6
- raiden-baileys@2.1.5
- @prototypevip/baileys@0.1.6
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.