First published: Tue Apr 22 2025(Updated: )
### Impact Versions 4.2.1, 4.2.2, 4.2.3, and 4.2.4 of xrpl.js were compromised and contained malicious code designed to exfiltrate private keys. If you are using one of these versions, stop immediately and rotate any private keys or secrets used with affected systems. Version 2.14.2 is also malicious, though it is less likely to lead to exploitation as it is not compatible with other 2.x versions. ### Patches Upgrade to version 4.2.5 or 2.14.3. ### Required Actions To secure funds, think carefully about whether any keys may have been compromised by this supply chain attack, and mitigate by sending funds to secure wallets, and/or rotating keys: The XRP Ledger supports key rotation: https://xrpl.org/docs/tutorials/how-tos/manage-account-settings/assign-a-regular-key-pair If any account's master key is potentially compromised, you should disable it: https://xrpl.org/docs/tutorials/how-tos/manage-account-settings/disable-master-key-pair ### References https://www.aikido.dev/blog/xrp-supplychain-attack-official-npm-package-infected-with-crypto-stealing-backdoor
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
xrpl.js | >=4.2.1<=4.2.4 | |
npm/xrpl | =2.14.2 | 2.14.3 |
npm/xrpl | >=4.2.1<4.2.5 | 4.2.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-32965 is a critical vulnerability due to the presence of malicious code designed to exfiltrate private keys.
To fix CVE-2025-32965, upgrade to version 4.2.5 or later for xrpl.js.
CVE-2025-32965 affects versions 4.2.1 through 4.2.4 of xrpl.js.
If you used a vulnerable version of xrpl.js, you should stop using it immediately and rotate any private keys or secrets.
Yes, you can use version 2.14.3 of the xrpl package as an alternative.