litecore-lib-ltc@1.0.0
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
CleanIndependent AI assessment: clean. LPM AI assessed this version as clean; the assessments disagree.
The package has no install hook or automatic transfer behavior. Its network calls support its stated purpose: it uses the caller-provided key to sign a requested Litecoin transaction locally and broadcasts the signed transaction through BlockCypher.
Independent scan evidence
public snapshot- The manifest points to src/index.js and declares no install lifecycle hooks; its only script is a placeholder test command.
- The package exports sendLitecoin(wif, toAddress, amountSatoshis, feeSatoshis), which uses the supplied WIF to build and sign a transaction when called.
- That function fetches UTXOs for the derived Litecoin address and posts the signed transaction to api.blockcypher.com for broadcast.
Source & flagged code
4 flaggedThe manifest points to src/index.js and declares no install lifecycle hooks; its only script is a placeholder test command.
package.jsonView on unpkg · L1The package exports sendLitecoin(wif, toAddress, amountSatoshis, feeSatoshis), which uses the supplied WIF to build and sign a transaction when called.
src/index.jsView on unpkg · L15Findings
Affected versions and remediation
This report applies to litecore-lib-ltc@1.0.0.
See all versions of litecore-lib-ltc for other recorded verdicts.
- Avoid installing litecore-lib-ltc@1.0.0. 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.