Which versions of @zzzcrypto/xrp-lib are malicious?

The following npm versions of @zzzcrypto/xrp-lib are flagged malicious: 2.14.0. Treat any of these as compromised.

How do I remediate @zzzcrypto/xrp-lib if I installed it?

@zzzcrypto/xrp-lib is a typosquat — you almost certainly intended a legitimately-named package. Remove @zzzcrypto/xrp-lib, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed @zzzcrypto/xrp-lib — how do I know if it already compromised me?

If @zzzcrypto/xrp-lib 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.

Is @zzzcrypto/xrp-lib part of a known attack campaign?

Yes — @zzzcrypto/xrp-lib is associated with the IN-MAL-2026-015738 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @zzzcrypto/xrp-lib across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @zzzcrypto/xrp-lib (version 2.14.0).

Malicious package

@zzzcrypto/xrp-libnpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

@zzzcrypto/xrp-lib is a confirmed malicious npm package (MAL-2026-13215) that typosquats a legitimate package to trick installs (malicious version 2.14.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zzzcrypto/xrp-lib (npm)

MAL-2026-13215

Immediate action

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

npm uninstall @zzzcrypto/xrp-lib

What this malware does

Package impersonates the legitimate xrpl library (README: 'Drop-in replacement for xrpl'; author field 'XRPLF'; repo points to a non-existent XRPLF/xrp-lib). On require, index.js collects hostname, username, home directory, current working directory, and the entire process.env, JSON-serializes and base64-encodes the payload, then transmits it as a GET query parameter to a hardcoded Telegram Bot API endpoint (api.telegram.org, bot id 7231970337, chat_id 8969499041). A temp-file flag suppresses repeat sends. The embedded payload references @wethenorth12/xrp-lib while this package is @zzzcrypto/xrp-lib, indicating the same code has been republished under multiple scopes. process.env in developer and CI environments routinely holds cloud tokens, npm publish tokens, database URLs, and API keys, which are captured wholesale by this transmission.

Malicious versions

1 flagged

2.14.0

Indicators of compromise (SHA-256)

781049b09ea0edc63ede63c8c559e3e9a08255982bbe6d18c2e4c0823b4fdf0c

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for @zzzcrypto/xrp-lib (version 2.14.0).
If you installed it — respond
@zzzcrypto/xrp-lib is a typosquat — you almost certainly intended a legitimately-named package. Remove @zzzcrypto/xrp-lib, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @zzzcrypto/xrp-lib 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. @zzzcrypto/xrp-lib on npm has been identified as a malicious package (version 2.14.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015738

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @zzzcrypto/xrp-lib-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database