CVE-2025-32965
Published: 22 April 2025
Summary
CVE-2025-32965 is a critical-severity Embedded Malicious Code (CWE-506) vulnerability in Xrpl (inferred from references). Its CVSS base score is 9.3 (Critical).
Operationally, ranked in the top 45.5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-12259
Vulnerability details
xrpl.js is a JavaScript/TypeScript API for interacting with the XRP Ledger in Node.js and the browser. 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. Version 2.14.2 is also malicious,…
more
though it is less likely to lead to exploitation as it is not compatible with other 2.x versions. Anyone who used one of these versions should stop immediately and rotate any private keys or secrets used with affected systems. Users of xrpl.js should pgrade to version 4.2.5 or 2.14.3 to receive a patch. 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. If any account's master key is potentially compromised, disable the key.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Restricting software to licensed versions and controlling P2P prevents introduction of software containing embedded malicious code from unauthorized sources.
The control prevents users from installing software that contains embedded malicious code.
Regular inventory reviews and updates make it harder to conceal or exploit embedded malicious code by requiring all components to be documented and accounted for.
Reverting to a known state removes any malicious code embedded by an attacker.
The approval and review process for maintenance tools can prevent introduction or continued use of tools containing embedded malicious code.
Supply chain strategy requires vetting and controls during acquisition to prevent or detect insertion of malicious code by vendors or integrators.
Background screening for development or deployment roles makes intentional insertion of malicious code by insiders materially harder to accomplish.
The capability explicitly searches for embedded malicious code and backdoors as indicators of compromise.