# Urgent Security Update for XRP Ledger: Node Operators Must Take Action Critical patch released to counter manifest flood attack targeting XRPL nodes. - **Source:** [News - Cryptonews](https://brifing.si/source/42333b6f-1c05-4a49-9914-7553e71d2223) - **Published:** 2026-08-03 - **Topic:** [Finance](https://brifing.si/c/finance) - **Original article:** - **On Brifing:** https://brifing.si/s/4643622d-0089-4856-b95b-03f2ad4bf00b ## Emergency: XRPL Nodes Under Attack A 'manifest flood' attack detected on July 31 targeted resource exhaustion of XRP Ledger nodes. Ripple's Engineering Director Vijay Khanna urgently called all node operators to upgrade to xrpld 3.2.1 on August 1-2. While ledger transactions continued uninterrupted, unpatched nodes remain at risk of resource depletion. XRP price dropped 1.5% to $1.06 amid these developments. ## Technical Details of the Attack The attack exploited a structural flaw in how XRPL nodes processed validator manifests. Pre-patch, nodes would accept and cache unlimited manifests tied to unknown validator keys. This allowed bad actors to flood nodes with fake manifests consuming memory, storage and bandwidth. Experts classify this more as a resource-draining DoS attempt than a consensus attack. ## Four Key Protections in the Hotfix Version 3.2.1 introduces four safeguards: Oversized manifests now get rejected outright. Manifest batches per network message are capped. Manifest data shared with new peers is limited. Unknown-key manifest cache is hard-capped at 100 entries. Additionally, unknown validator manifests no longer get written to disk. These changes significantly improve nodes' resistance to resource exhaustion. ## Correct Update Procedure Operators must follow a two-step process: First install 3.2.1, let server run for 1-2 minutes, then perform a second restart. This second step clears any pre-patch manifest data. Ripple also advises operators to verify they trust Ripple's current GPG signing key (rotated Feb 18, 2026) to prevent silent update failures. ## Who Needs to Act Immediately? Exchanges, custodians, wallet providers, data services and any business running XRPL servers must update urgently. Regular XRP holders don't need to move funds. Adoption speed concerns remain; while v3.2.0 spread quickly among validators since June 15, broader node network adoption has been slower, leaving some operators doubly exposed. ## XRP Ecosystem Growth Context The incident occurred amid XRP Ledger's expansion. Coinpaper data shows the network added 490,000 new accounts in H1 2026, surpassing 8.4M total accounts. This growth transforms infrastructure security from edge-case concern to structural necessity. Institutional developments like Aviva's tokenized liquidity fund on XRPL raise stakes for delayed patching. ## Broader Blockchain Security Implications The manifest flood establishes a new pattern in blockchain vulnerabilities - showing how unbounded auxiliary data channels can be exploited even with intact consensus logic. XRPL Operations will publish a technical post-mortem detailing attacker behavior, traffic volumes and additional hardening steps. This signals the team treats it as formal security incident rather than routine maintenance. ## Conclusions and Takeaways XRPL security team's rapid response and targeted patch strategy deserve credit. However, node operators' update compliance speed underscores decentralized network security awareness importance. With 2026 growth figures expanding XRP Ledger's financial infrastructure role, security measures must evolve accordingly. This incident serves as crucial lesson about proactive security policies for blockchain operators. ## Sources covering this story - https://cryptonews.com/news/xrp-news-xrpld-3-2-1-hotfix-manifest-flood-xrpl/ — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._