litecore-lib-ltc@1.9.7
Litecoin utility functions for transaction creation, signing, and broadcasting.
OpenSSF/OSV Malicious Advisory
imported 3d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18442 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
This is a serious private-key disclosure in the explicit transfer path, but the source does not show the key being sent to a remote host or exposed automatically at install or import. Treat it as a security risk warranting a warning rather than a confirmed malicious attack.
Independent scan evidence
public snapshot- The package loads src/index.js as its main entry and declares no install lifecycle hook.
- LitecoinWallet.send prints this.privateKey.toString() to stdout before validating and processing a transfer.
- The wallet constructor obtains and retains a private key from the supplied WIF.
- The send method signs the transaction and then broadcasts it through the BlockCypher API.
- Balance lookup contacts BlockCypher and CoinGecko for the requested address balance and Litecoin price.
- The private-key disclosure occurs when send or sendMax is called, rather than during installation or module import.
- The API requests use public blockchain and market-price endpoints for the package’s stated wallet functions.
Source & flagged code
6 flaggedThe package loads src/index.js as its main entry and declares no install lifecycle hook.
package.jsonView on unpkg · L2LitecoinWallet.send prints this.privateKey.toString() to stdout before validating and processing a transfer.
src/index.jsView on unpkg · L25Findings
Affected versions and remediation
This report applies to litecore-lib-ltc@1.9.7.
See all versions of litecore-lib-ltc for other recorded verdicts.
- Avoid installing litecore-lib-ltc@1.9.7. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.