In a significant security breach, the widely-used Ripple’s xrpl.js npm package was backdoored by unknown attackers, compromising specific versions to steal private keys. This alarming incident impacts the XRP Ledger, a blockchain platform launched by Ripple Labs. The attack was initiated on April 21, 2025, and involved adding malicious code intended to transmit stolen private keys to an external domain. The compromised package spans versions 4.2.1 through 4.2.4 and 2.14.2, highlighting a critical lapse in security for a library with over 2.9 million downloads. The backdoor deployment points to a potential hack of a Ripple employee’s npm account, possibly that of “mukulljangid.” Despite these modifications, there has been no evidence of changes to the associated GitHub repository.
Nature of the Compromise
The compromised xrpl.js package includes a function named checkValidityOfSeed, designed to exfiltrate private keys to an external server. The introduction of this backdoor appears to have been conducted surreptitiously over multiple releases of the package. This attack serves as a grim reminder of the persistent vulnerability in software supply chains, even among well-established and frequently-used libraries. The package’s widespread use exacerbates the potential damage, underlining the urgency of addressing such security gaps. Affected users have been advised to update to versions 4.2.5 and 2.14.3 to mitigate exposure to this breach. Security firm Aikido Security has emphasized the importance of this update to prevent further compromise.
The XRP Ledger Foundation has reassured users that while xrpl.js was compromised, the XRP Ledger codebase itself remains unaffected and secure. This distinction is crucial in maintaining user confidence amid the breach. GitHub has also released an advisory confirming the malicious nature of certain versions and urging users to discontinue their use immediately and rotate private keys as a precautionary measure. This step is vital in preventing unauthorized access and further exploitation of the stolen private keys. The assignment of CVE-2025-32965 to this incident, with a high CVSS score of 9.3, highlights the severity and urgency of the threat.
User and Industry Response
Given the magnitude of this security breach, users are being urged to take immediate action to secure their systems and data. Migrating to the secure versions 4.2.5 and 2.14.3 of the xrpl.js library is an essential first step. Additionally, users must reassess their security protocols to ensure they are robust enough to withstand similar attacks in the future. This breach has exposed significant flaws in the dependency management practices that many developers rely on, calling for a deeper evaluation of security measures across the board.
The incident has also prompted broader discussions within the software development community about the importance of securing the software supply chain. Enhanced verification processes, stricter access controls for npm accounts, and regular security audits are some of the measures being advocated to prevent such incidents. Developers are encouraged to stay vigilant and proactive in identifying and mitigating potential security threats. By adopting a comprehensive approach to security, the risks associated with such supply chain attacks can be significantly reduced.
Lessons Learned and Future Precautions
In a major security incident, Ripple’s widely-used xrpl.js npm package was breached by unknown attackers, compromising certain versions to steal private keys. This troubling event affects the XRP Ledger, a blockchain platform launched by Ripple Labs. The attack began on April 21, 2025, with the insertion of malicious code designed to transmit stolen private keys to an external site. Versions 4.2.1 through 4.2.4 and 2.14.2 of the package were compromised, underscoring a severe security failure for a library with over 2.9 million downloads. The backdoor suggests a possible hack of a Ripple employee’s npm account, potentially that of “mukulljangid.” Despite these malicious alterations, there has been no indication of changes to the corresponding GitHub repository. This breach highlights the critical need for robust security practices in software distribution, especially for widely trusted components. Ripple Labs is now likely to face scrutiny over their internal security procedures to prevent future occurrences.