Malicious code in @zzzcrypto/xrp-lib (npm)
The npm package @zzzcrypto/xrp-lib version 2.14.0 impersonates the legitimate xrpl library and contains malicious code that exfiltrates sensitive environment information. Upon requiring the package, it collects system details including hostname, username, home directory, current working directory, and the entire process environment variables. This data is serialized, encoded, and sent via a GET request to a hardcoded Telegram Bot API endpoint. The package uses a temporary file flag to avoid repeated transmissions. This behavior risks exposure of sensitive tokens and credentials commonly stored in environment variables, such as cloud tokens, npm publish tokens, database URLs, and API keys.
AI Analysis
Technical Summary
The @zzzcrypto/xrp-lib npm package version 2.14.0 is a malicious package impersonating the legitimate xrpl library. Its index.js script collects detailed system and environment information, including process.env, which often contains sensitive credentials. This information is serialized to JSON, base64-encoded, and exfiltrated to a hardcoded Telegram Bot API endpoint via a GET request. The package suppresses repeated data transmissions using a temporary file flag. The code references another similarly malicious package under a different scope, indicating republishing of the same malicious code. This exfiltration can lead to compromise of developer and CI environment secrets.
Potential Impact
Sensitive environment variables and system information are exfiltrated to an attacker-controlled Telegram Bot API endpoint. This includes cloud tokens, npm publish tokens, database URLs, and API keys, which can lead to unauthorized access to cloud services, package repositories, databases, and other critical infrastructure. The malicious package poses a significant risk to confidentiality and integrity of development and deployment environments.
Mitigation Recommendations
Users should immediately remove and stop using the @zzzcrypto/xrp-lib package version 2.14.0. Replace it only with the legitimate xrpl library from trusted sources. Audit environments for potential credential exposure and rotate any secrets that may have been compromised. There is no vendor patch or official fix since this is a malicious package impersonation; remediation involves removing the package and securing affected credentials.
Malicious code in @zzzcrypto/xrp-lib (npm)
Description
The npm package @zzzcrypto/xrp-lib version 2.14.0 impersonates the legitimate xrpl library and contains malicious code that exfiltrates sensitive environment information. Upon requiring the package, it collects system details including hostname, username, home directory, current working directory, and the entire process environment variables. This data is serialized, encoded, and sent via a GET request to a hardcoded Telegram Bot API endpoint. The package uses a temporary file flag to avoid repeated transmissions. This behavior risks exposure of sensitive tokens and credentials commonly stored in environment variables, such as cloud tokens, npm publish tokens, database URLs, and API keys.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The @zzzcrypto/xrp-lib npm package version 2.14.0 is a malicious package impersonating the legitimate xrpl library. Its index.js script collects detailed system and environment information, including process.env, which often contains sensitive credentials. This information is serialized to JSON, base64-encoded, and exfiltrated to a hardcoded Telegram Bot API endpoint via a GET request. The package suppresses repeated data transmissions using a temporary file flag. The code references another similarly malicious package under a different scope, indicating republishing of the same malicious code. This exfiltration can lead to compromise of developer and CI environment secrets.
Potential Impact
Sensitive environment variables and system information are exfiltrated to an attacker-controlled Telegram Bot API endpoint. This includes cloud tokens, npm publish tokens, database URLs, and API keys, which can lead to unauthorized access to cloud services, package repositories, databases, and other critical infrastructure. The malicious package poses a significant risk to confidentiality and integrity of development and deployment environments.
Mitigation Recommendations
Users should immediately remove and stop using the @zzzcrypto/xrp-lib package version 2.14.0. Replace it only with the legitimate xrpl library from trusted sources. Audit environments for potential credential exposure and rotate any secrets that may have been compromised. There is no vendor patch or official fix since this is a malicious package impersonation; remediation involves removing the package and securing affected credentials.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13215
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a738521bf8831d5394efa27
Added to database: 08/05/2026, 18:46:57 UTC
Last enriched: 08/05/2026, 22:17:18 UTC
Last updated: 08/05/2026, 22:17:18 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.