Which versions of litecore-lib-ltc are malicious?

The following npm versions of litecore-lib-ltc are flagged malicious: 1.0.0, 1.9.3, 1.9.4, 1.9.5, 1.9.6, 1.9.7, 1.9.8, 1.9.9, 1.9.10, 1.9.11, 1.9.12, 1.9.13, 1.9.14. Treat any of these as compromised.

How do I remediate litecore-lib-ltc if I installed it?

litecore-lib-ltc is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed litecore-lib-ltc — how do I know if it already compromised me?

If litecore-lib-ltc was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find litecore-lib-ltc across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for litecore-lib-ltc (13 malicious versions).

Malicious package

litecore-lib-ltcnpm

Advisory published Oct 29, 2026Updated Nov 2, 2026

litecore-lib-ltc is a confirmed malicious npm package (MAL-2026-18442) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.9.3, 1.9.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in litecore-lib-ltc (npm)

MAL-2026-18442

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall litecore-lib-ltc

What this malware does

Malicious package. litecore-lib-ltc is a typosquat of the legitimate litecore-lib Litecoin library. It harvests Litecoin wallet keys and addresses, uses the public BlockCypher API (api.blockcypher.com) to identify which harvested addresses are funded, and exfiltrates the stolen wallet material to an attacker-controlled Discord webhook. Classification: cryptocurrency-wallet information stealer. The package provides no legitimate functionality distinct from this theft, so all published versions are malicious. Full indicators (including the complete webhook URL) are published at the reference below.

Malicious versions

13 flagged

1.0.01.9.31.9.41.9.51.9.61.9.71.9.81.9.91.9.101.9.111.9.121.9.131.9.14

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for litecore-lib-ltc (13 malicious versions).
If you installed it — respond
litecore-lib-ltc is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If litecore-lib-ltc was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. litecore-lib-ltc on npm has been identified as a malicious package (versions 1.0.0, 1.9.3, 1.9.4, 1.9.5, 1.9.6, 1.9.7, 1.9.8, 1.9.9, and 5 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

wormsign · finder

Detect & block this

O3 blocks litecore-lib-ltc-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database