npm

The litecore-lib-ltc npm Attack

Updated 19 Nov 2026 · Incident date 1 Mar 2026

The npm package litecore-lib-ltc posed as a Litecoin library and sent wallet keys and addresses to a Discord webhook.

The package had real installs and npm removed every release on 19 November 2026. Litecoin developers and wallet users who installed it were at risk.

What happened

The OpenSSF malicious packages database describes litecore-lib-ltc as a typosquat of the legitimate litecore-lib Litecoin library.

  • It harvested Litecoin wallet keys and addresses.
  • It used the public BlockCypher API at api.blockcypher.com to find which harvested addresses hold funds.
  • It sent the stolen wallet material to an attacker-controlled Discord webhook.
  • The record says the package gave no working Litecoin functionality.
  • npm now holds the name and serves the placeholder 0.0.1-security. The registry marked it a security holding package and set the maintainer to npm.

Affected versions

  • 1.0.0 went up on 1 March 2026 at 22:23 UTC.
  • Versions 1.9.3 to 1.9.14 followed on 1 and 2 March 2026. 1.9.14 appeared at 00:17 UTC on 2 March 2026.
  • The OpenSSF record lists all 13 of these versions and gives the range >= 0. No fixed version exists.
  • 0.0.1-security is the registry placeholder, not a restored original release.

Indicators of compromise

  • Exfiltration endpoint: https://discord.com/api/webhooks/1477797533999956131/
  • Balance lookups to api.blockcypher.com from the package.

How to check

Check your project dependency tree for the package. This command reads installed metadata and does not run the package.

npm ls litecore-lib-ltc

Check your CI build logs and lockfile history for versions 1.0.0 to 1.9.14. The registry no longer serves those releases, so a clean install today cannot rule out earlier exposure.

What to do now

  1. Remove the package from every project that uses it.
  2. Move funds from any Litecoin wallet on an affected machine to a new wallet with new keys.
  3. From a clean machine, rotate other secrets and keys stored on the affected machine.
  4. Treat a machine that installed or ran an affected release as compromised, as the GitHub advisory advises.

What Vigilance would show

These examples show an install hold and the corresponding owner report.

Example install message

Vigilance blocked `litecore-lib-ltc` 1.9.14. This version is too new or changed in a way Vigilance must check first.

Example owner report

Bad update

litecore-lib-ltc 1.9.14

The npm package litecore-lib-ltc posed as a Litecoin library and sent wallet keys and addresses to a Discord webhook.

See what to do now.

No security team? See who reads the alert.

Frequently asked questions

What did the malicious code do?

The OpenSSF record says it harvested Litecoin wallet keys and addresses, checked them against the BlockCypher API and sent the results to a Discord webhook. The removed releases were unavailable for code inspection, so this page reports the advisory findings.

Is the real litecore-lib package affected?

No. The OpenSSF record describes litecore-lib-ltc as a typosquat of the legitimate litecore-lib package. The legitimate package does not appear in the record.

Can I still download the package?

No. npm holds the name and serves only the placeholder 0.0.1-security. Every original release is gone from the registry.

Sources

  1. raw.githubusercontent.com/ossf/malicious-packages/main/osv/malicious/npm/litecore-lib-ltc/MAL-2026-18442.json
  2. github.com/advisories/GHSA-448f-g3c2-cq9v
  3. registry.npmjs.org/litecore-lib-ltc

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · npm supply chain attacks · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library