CVE-2025-32965

Description

### 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

How to fix CVE-2025-32965

To remediate CVE-2025-32965, upgrade the affected package to a fixed version below.

• —upgrade to 4.2.5 or later

Is CVE-2025-32965 being exploited?

Low — EPSS is 0.3%, meaning exploitation activity has not been observed at scale.

Affected packages (1)

• >= 4.2.1, < 4.2.5

CVSS scores

References (6)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2025-32965
• PATCHgithub.com/XRPLF/xrpl.js
• WEBgithub.com/XRPLF/xrpl.js/security/advisories/GHSA-33qr-m49q-rxfx
• WEBwww.aikido.dev/blog/xrp-supplychain-attack-official-npm-package-infected-with-crypto-stealing-backdoor