198,715.88 XRP<\/strong>.<\/p>\n\n\n\nThe bridge remains offline while developers continue reviewing security improvements and evaluate possible compensation options for affected users.<\/p>\n\n\n\n
Tx also said it has traced the stolen funds across multiple blockchains and submitted a complaint to the FBI\u2019s Internet Crime Complaint Center, or IC3.<\/p>\n\n\n\n
Faulty bridge logic allowed fake XRP deposits<\/h2>\n\n\n\n
The exploit centered on how Tx\u2019s bridge relayers verified XRP deposits.<\/p>\n\n\n\n
Normally, the bridge should confirm that XRP has actually arrived at the correct destination before minting an equivalent amount of bridged XRP on the Tx network.<\/p>\n\n\n\n
In this case, that verification process failed.<\/p>\n\n\n\n
Tx said the relayers accepted transactions containing the expected bridge memo without properly confirming that the XRP had been sent to the bridge\u2019s actual vault address.<\/p>\n\n\n\n
That meant an attacker could create transactions that appeared valid to the bridge software even though no XRP reached the reserve.<\/p>\n\n\n\n
Once enough relayers approved those transactions, the bridge treated them as legitimate deposits and issued unbacked bridged XRP.<\/p>\n\n\n\n
The attacker could then use those artificial balances to withdraw genuine XRP from the bridge reserve.<\/p>\n\n\n\n
In simple terms, the attacker was able to convince the bridge that XRP had been deposited when it had not.<\/p>\n\n\n\n
Tx says XRP Ledger itself was not compromised<\/h2>\n\n\n\n
One of the most important findings from the investigation is that the exploit did not result from a vulnerability in the XRP Ledger.<\/p>\n\n\n\n
Tx described the issue as isolated to its bridge software.<\/p>\n\n\n\n
Bashash said the vulnerability involved XRPL relayer logic connected to cross-currency payments and the network\u2019s DefaultRipple feature.<\/p>\n\n\n\n
However, later ledger analysis showed that DefaultRipple itself did not directly cause native XRP to leave the bridge.<\/p>\n\n\n\n
Instead, the main problem was insufficient destination verification by the bridge relayers.<\/p>\n\n\n\n
That distinction is important because it means the underlying XRP Ledger continued functioning as intended while the application built on top of it incorrectly interpreted transactions.<\/p>\n\n\n\n
Relayers approved invalid deposits<\/h2>\n\n\n\n
Independent analysis of the incident found additional evidence pointing toward a shared verification failure rather than stolen private keys.<\/p>\n\n\n\n
The bridge reportedly used a multisignature setup to approve XRP withdrawals.<\/p>\n\n\n\n
Analysis showed that 17 of 28 relayers signed the bridge payouts<\/strong>, while 21 relayers reportedly approved the attacker\u2019s first false deposit.<\/p>\n\n\n\nThat suggests the attacker did not need to steal the bridge’s signing keys.<\/p>\n\n\n\n
Instead, multiple relayers were running logic that incorrectly accepted the same invalid transaction.<\/p>\n\n\n\n
Once enough of those relayers agreed that a deposit was legitimate, the bridge automatically released real XRP.<\/p>\n\n\n\n
This type of failure highlights one of the major risks of cross-chain bridges: even when the underlying blockchains remain secure, faulty software that interprets transactions between networks can create vulnerabilities.<\/p>\n\n\n\n
Nearly 200,000 XRP was removed from the reserve<\/h2>\n\n\n\n
Earlier public ledger analysis identified 199,916.3 XRP<\/strong> leaving the bridge reserve through 94 payments over approximately 97 minutes.<\/p>\n\n\n\nTx’s technical lead later placed the stolen amount at 198,715.88 XRP<\/strong>.<\/p>\n\n\n\nThat creates a difference of roughly 1,200 XRP between the amount observed leaving the bridge and the amount currently described as stolen.<\/p>\n\n\n\n
Tx has not publicly explained that difference.<\/p>\n\n\n\n
The discrepancy may eventually be clarified as the team completes its final reconciliation of the exploit.<\/p>\n\n\n\n
For affected users, the more important issue is that bridged XRP on the Tx network is currently not completely backed by real XRP reserves.<\/p>\n\n\n\n
Tx said other bridged assets remain fully backed.<\/p>\n\n\n\n
DefaultRipple was not responsible for draining native XRP<\/h2>\n\n\n\n
Initial discussions surrounding the exploit focused heavily on DefaultRipple.<\/p>\n\n\n\n
DefaultRipple is an XRP Ledger feature related primarily to issued assets and how those assets can move between trust lines.<\/p>\n\n\n\n
However, analysis from XRPL.to concluded that native XRP did not leave the bridge because of rippling.<\/p>\n\n\n\n
All of the XRP withdrawals observed during the incident were authorized through the bridge’s own multisignature system.<\/p>\n\n\n\n
That means DefaultRipple may have been involved in creating the conditions that confused the relayer logic, but it was not itself responsible for moving XRP out of the reserve.<\/p>\n\n\n\n
The failure occurred when the bridge software incorrectly interpreted transactions and allowed them to count as deposits.<\/p>\n\n\n\n
This distinction helps separate a bridge-specific security issue from a vulnerability in XRP’s underlying blockchain.<\/p>\n\n\n\n
Attacker converted XRP into ETH<\/h2>\n\n\n\n
After obtaining the XRP, the attacker began moving the stolen funds across different blockchain networks.<\/p>\n\n\n\n
Bashash said the XRP was converted into ETH before being routed through THORChain<\/strong>.<\/p>\n\n\n\nThe assets were then transferred to Ethereum and eventually sent into Tornado Cash<\/strong>.<\/p>\n\n\n\nTornado Cash is a privacy-focused protocol that makes it significantly more difficult to follow the movement of funds after they enter its pools.<\/p>\n\n\n\n
Investigators can still examine the blockchain transactions that occurred before the assets reached Tornado Cash, but tracing becomes more complicated afterward.<\/p>\n\n\n\n
The movement of the funds suggests the attacker quickly attempted to reduce the ability of investigators and blockchain analytics firms to follow the stolen assets.<\/p>\n\n\n\n
Tx files FBI IC3 complaint<\/h2>\n\n\n\n
Tx said it has formally reported the incident to the FBI’s Internet Crime Complaint Center.<\/p>\n\n\n\n
According to the project, its IC3 complaint included blockchain transaction records along with additional information that could potentially help identify those responsible for the exploit.<\/p>\n\n\n\n
Submitting an IC3 complaint allows information about suspected cybercrime to be shared with U.S. law enforcement.<\/p>\n\n\n\n
However, filing the complaint does not automatically mean the FBI has opened a formal criminal investigation.<\/p>\n\n\n\n
Whether law enforcement pursues the case further will depend on the information available and the continuing investigation.<\/p>\n\n\n\n
Tx said it intends to continue working toward identifying and prosecuting the attacker.<\/p>\n\n\n\n
Cross-chain bridges remain major hacking targets<\/h2>\n\n\n\n
The Tx incident is part of a much broader pattern involving cross-chain bridge security.<\/p>\n\n\n\n
Bridges allow assets to move between different blockchain networks.<\/p>\n\n\n\n
To make that process work, bridge systems must confirm that assets have been locked or deposited on one blockchain before issuing corresponding assets on another.<\/p>\n\n\n\n
If that verification system fails, attackers may be able to mint assets that are not backed by real reserves.<\/p>\n\n\n\n
Cross-chain bridge exploits have reportedly caused more than $4 billion in losses since 2021<\/strong>.<\/p>\n\n\n\nMany of the largest incidents have involved weaknesses in transaction verification, validator systems, smart contracts or private-key management.<\/p>\n\n\n\n
The Tx exploit appears to fall into the verification category.<\/p>\n\n\n\n
The attacker did not need to compromise the XRP Ledger itself. Instead, they exploited the software responsible for deciding whether an XRP transaction represented a legitimate bridge deposit.<\/p>\n\n\n\n
Bridged XRP is currently not fully backed<\/h2>\n\n\n\n
One of the most important consequences of the exploit is the reserve shortfall created for bridged XRP.<\/p>\n\n\n\n
Because the attacker was able to mint unbacked balances and redeem them for genuine XRP, the amount of XRP held by the bridge is now lower than the quantity needed to fully support every bridged XRP token.<\/p>\n\n\n\n
Tx has acknowledged that bridged XRP is currently not fully reserve-backed.<\/p>\n\n\n\n
Other assets supported by the bridge remain fully collateralized, according to the project.<\/p>\n\n\n\n
The bridge has therefore remained halted while developers determine how to restore safe operations and address the reserve deficit.<\/p>\n\n\n\n
Tx says vulnerable code has been fixed<\/h2>\n\n\n\n
Tx said it has identified and remedied the software responsible for the exploit.<\/p>\n\n\n\n
However, the XRPL bridge has not yet resumed operations.<\/p>\n\n\n\n
The team is conducting additional security reviews before deciding when it is safe to reopen the service.<\/p>\n\n\n\n
That approach suggests Tx wants to examine whether similar weaknesses could exist elsewhere in the bridge rather than simply fixing the individual bug that was exploited.<\/p>\n\n\n\n
No reopening date has been announced.<\/p>\n\n\n\n
For users, that means XRP transfers through the affected bridge remain unavailable for now.<\/p>\n\n\n\n
User compensation plan is still being evaluated<\/h2>\n\n\n\n
Tx is also examining possible ways to address losses experienced by bridged XRP holders.<\/p>\n\n\n\n
The project has not yet announced a final reimbursement or recovery mechanism.<\/p>\n\n\n\n
It said additional information about the process and expected timeline will be released in a future update.<\/p>\n\n\n\n
Until then, the company says affected users do not need to take any action.<\/p>\n\n\n\n
Tx has also warned users to avoid unofficial recovery services.<\/p>\n\n\n\n
That warning is particularly important after major crypto exploits because scammers often impersonate project teams or security companies and claim they can recover stolen funds.<\/p>\n\n\n\n
Users should therefore rely only on official Tx communications regarding any future compensation process.<\/p>\n\n\n\n
What happens next<\/h2>\n\n\n\n
Several important questions remain unanswered following the exploit.<\/p>\n\n\n\n
The first is the exact amount of XRP ultimately considered stolen.<\/p>\n\n\n\n
Tx currently puts the figure at 198,715.88 XRP, while public ledger analysis previously tracked 199,916.3 XRP leaving the reserve.<\/p>\n\n\n\n
A final reconciliation should clarify the difference.<\/p>\n\n\n\n
The second issue is whether any stolen assets can still be recovered or frozen.<\/p>\n\n\n\n
Because the attacker moved the funds through multiple networks before eventually using Tornado Cash, recovery could be difficult.<\/p>\n\n\n\n
Another major question concerns affected users.<\/p>\n\n\n\n
Tx has said it is exploring possible remedies but has not yet explained how the XRP reserve shortfall will be covered.<\/p>\n\n\n\n
Finally, the project must determine when the XRPL bridge can safely reopen.<\/p>\n\n\n\n
The vulnerable code has reportedly been fixed, but additional audits and security improvements may be necessary before operations resume.<\/p>\n\n\n\n
For now, the exploit appears to be a bridge-specific failure rather than a compromise of the XRP Ledger.<\/p>\n\n\n\n
But the incident once again shows how a relatively small error in cross-chain verification logic can create significant financial losses even when the underlying blockchain remains secure.<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Tx has released new details about the exploit that drained nearly 200,000 XRP from its XRPL bridge, confirming that the attack was caused by a flaw in the bridge\u2019s deposit verification logic rather than a vulnerability in the XRP Ledger itself. The incident took place on Aug. 9, when an attacker exploited faulty relayer checks…<\/p>\n","protected":false},"author":3,"featured_media":16002,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[63,70],"tags":[293,2082,321],"class_list":["post-16001","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-crypto-news","category-finance","tag-crypto-hack","tag-fbi","tag-xrp"],"yoast_head":"\n
XRP bridge exploit update: Tx identifies flaw, alerts FBI - Crypto News<\/title>\n<meta name=\"description\" content=\"XRP bridge exploit drained 198,715 XRP after faulty deposit checks. Tx traced funds through Tornado Cash and filed an FBI IC3 complaint.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/cryptonewsdesk.com\/index.php\/2026\/08\/12\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"XRP bridge exploit update: Tx identifies flaw, alerts FBI - Crypto News\" \/>\n<meta property=\"og:description\" content=\"XRP bridge exploit drained 198,715 XRP after faulty deposit checks. Tx traced funds through Tornado Cash and filed an FBI IC3 complaint.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cryptonewsdesk.com\/index.php\/2026\/08\/12\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\/\" \/>\n<meta property=\"og:site_name\" content=\"Crypto News\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-12T20:40:07+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-12T20:40:10+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/cryptonewsdesk.com\/wp-content\/uploads\/2026\/08\/61.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1080\" \/>\n\t<meta property=\"og:image:height\" content=\"720\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Digital Vibe\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Digital Vibe\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/index.php\\\/2026\\\/08\\\/12\\\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/index.php\\\/2026\\\/08\\\/12\\\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\\\/\"},\"author\":{\"name\":\"Digital Vibe\",\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/#\\\/schema\\\/person\\\/56afc0b5a42e13762ccad410f131f96a\"},\"headline\":\"XRP bridge exploit update: Tx identifies flaw, alerts FBI\",\"datePublished\":\"2026-08-12T20:40:07+00:00\",\"dateModified\":\"2026-08-12T20:40:10+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/index.php\\\/2026\\\/08\\\/12\\\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\\\/\"},\"wordCount\":1633,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/index.php\\\/2026\\\/08\\\/12\\\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/cryptonewsdesk.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/61.png\",\"keywords\":[\"crypto hack\",\"FBI\",\"XRP\"],\"articleSection\":[\"Crypto News\",\"Finance\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/cryptonewsdesk.com\\\/index.php\\\/2026\\\/08\\\/12\\\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/index.php\\\/2026\\\/08\\\/12\\\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\\\/\",\"url\":\"https:\\\/\\\/cryptonewsdesk.com\\\/index.php\\\/2026\\\/08\\\/12\\\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\\\/\",\"name\":\"XRP bridge exploit update: Tx identifies flaw, alerts FBI - Crypto News\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/index.php\\\/2026\\\/08\\\/12\\\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/index.php\\\/2026\\\/08\\\/12\\\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/cryptonewsdesk.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/61.png\",\"datePublished\":\"2026-08-12T20:40:07+00:00\",\"dateModified\":\"2026-08-12T20:40:10+00:00\",\"description\":\"XRP bridge exploit drained 198,715 XRP after faulty deposit checks. Tx traced funds through Tornado Cash and filed an FBI IC3 complaint.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/index.php\\\/2026\\\/08\\\/12\\\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/cryptonewsdesk.com\\\/index.php\\\/2026\\\/08\\\/12\\\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/index.php\\\/2026\\\/08\\\/12\\\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\\\/#primaryimage\",\"url\":\"https:\\\/\\\/cryptonewsdesk.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/61.png\",\"contentUrl\":\"https:\\\/\\\/cryptonewsdesk.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/61.png\",\"width\":1080,\"height\":720,\"caption\":\"crypto\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/index.php\\\/2026\\\/08\\\/12\\\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/cryptonewsdesk.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"XRP bridge exploit update: Tx identifies flaw, alerts FBI\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/#website\",\"url\":\"https:\\\/\\\/cryptonewsdesk.com\\\/\",\"name\":\"Crypto News\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/cryptonewsdesk.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/#organization\",\"name\":\"Crypto News\",\"url\":\"https:\\\/\\\/cryptonewsdesk.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/cryptonewsdesk.com\\\/wp-content\\\/uploads\\\/2025\\\/04\\\/Crypto-NEWS.png\",\"contentUrl\":\"https:\\\/\\\/cryptonewsdesk.com\\\/wp-content\\\/uploads\\\/2025\\\/04\\\/Crypto-NEWS.png\",\"width\":500,\"height\":500,\"caption\":\"Crypto News\"},\"image\":{\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/company\\\/crypto-news-desk\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/cryptonewsdesk.com\\\/#\\\/schema\\\/person\\\/56afc0b5a42e13762ccad410f131f96a\",\"name\":\"Digital Vibe\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/37e93c2e55bfd306b5f3247c0ce7dba6687533106a6330857687e3dcd20fc018?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/37e93c2e55bfd306b5f3247c0ce7dba6687533106a6330857687e3dcd20fc018?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/37e93c2e55bfd306b5f3247c0ce7dba6687533106a6330857687e3dcd20fc018?s=96&d=mm&r=g\",\"caption\":\"Digital Vibe\"},\"url\":\"https:\\\/\\\/cryptonewsdesk.com\\\/index.php\\\/author\\\/digital-vibe\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"XRP bridge exploit update: Tx identifies flaw, alerts FBI - Crypto News","description":"XRP bridge exploit drained 198,715 XRP after faulty deposit checks. Tx traced funds through Tornado Cash and filed an FBI IC3 complaint.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/cryptonewsdesk.com\/index.php\/2026\/08\/12\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\/","og_locale":"en_US","og_type":"article","og_title":"XRP bridge exploit update: Tx identifies flaw, alerts FBI - Crypto News","og_description":"XRP bridge exploit drained 198,715 XRP after faulty deposit checks. Tx traced funds through Tornado Cash and filed an FBI IC3 complaint.","og_url":"https:\/\/cryptonewsdesk.com\/index.php\/2026\/08\/12\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\/","og_site_name":"Crypto News","article_published_time":"2026-08-12T20:40:07+00:00","article_modified_time":"2026-08-12T20:40:10+00:00","og_image":[{"width":1080,"height":720,"url":"https:\/\/cryptonewsdesk.com\/wp-content\/uploads\/2026\/08\/61.png","type":"image\/png"}],"author":"Digital Vibe","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Digital Vibe","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/cryptonewsdesk.com\/index.php\/2026\/08\/12\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\/#article","isPartOf":{"@id":"https:\/\/cryptonewsdesk.com\/index.php\/2026\/08\/12\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\/"},"author":{"name":"Digital Vibe","@id":"https:\/\/cryptonewsdesk.com\/#\/schema\/person\/56afc0b5a42e13762ccad410f131f96a"},"headline":"XRP bridge exploit update: Tx identifies flaw, alerts FBI","datePublished":"2026-08-12T20:40:07+00:00","dateModified":"2026-08-12T20:40:10+00:00","mainEntityOfPage":{"@id":"https:\/\/cryptonewsdesk.com\/index.php\/2026\/08\/12\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\/"},"wordCount":1633,"commentCount":0,"publisher":{"@id":"https:\/\/cryptonewsdesk.com\/#organization"},"image":{"@id":"https:\/\/cryptonewsdesk.com\/index.php\/2026\/08\/12\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\/#primaryimage"},"thumbnailUrl":"https:\/\/cryptonewsdesk.com\/wp-content\/uploads\/2026\/08\/61.png","keywords":["crypto hack","FBI","XRP"],"articleSection":["Crypto News","Finance"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/cryptonewsdesk.com\/index.php\/2026\/08\/12\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/cryptonewsdesk.com\/index.php\/2026\/08\/12\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\/","url":"https:\/\/cryptonewsdesk.com\/index.php\/2026\/08\/12\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\/","name":"XRP bridge exploit update: Tx identifies flaw, alerts FBI - Crypto News","isPartOf":{"@id":"https:\/\/cryptonewsdesk.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/cryptonewsdesk.com\/index.php\/2026\/08\/12\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\/#primaryimage"},"image":{"@id":"https:\/\/cryptonewsdesk.com\/index.php\/2026\/08\/12\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\/#primaryimage"},"thumbnailUrl":"https:\/\/cryptonewsdesk.com\/wp-content\/uploads\/2026\/08\/61.png","datePublished":"2026-08-12T20:40:07+00:00","dateModified":"2026-08-12T20:40:10+00:00","description":"XRP bridge exploit drained 198,715 XRP after faulty deposit checks. Tx traced funds through Tornado Cash and filed an FBI IC3 complaint.","breadcrumb":{"@id":"https:\/\/cryptonewsdesk.com\/index.php\/2026\/08\/12\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cryptonewsdesk.com\/index.php\/2026\/08\/12\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/cryptonewsdesk.com\/index.php\/2026\/08\/12\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\/#primaryimage","url":"https:\/\/cryptonewsdesk.com\/wp-content\/uploads\/2026\/08\/61.png","contentUrl":"https:\/\/cryptonewsdesk.com\/wp-content\/uploads\/2026\/08\/61.png","width":1080,"height":720,"caption":"crypto"},{"@type":"BreadcrumbList","@id":"https:\/\/cryptonewsdesk.com\/index.php\/2026\/08\/12\/xrp-bridge-exploit-update-tx-identifies-flaw-alerts-fbi\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/cryptonewsdesk.com\/"},{"@type":"ListItem","position":2,"name":"XRP bridge exploit update: Tx identifies flaw, alerts FBI"}]},{"@type":"WebSite","@id":"https:\/\/cryptonewsdesk.com\/#website","url":"https:\/\/cryptonewsdesk.com\/","name":"Crypto News","description":"","publisher":{"@id":"https:\/\/cryptonewsdesk.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/cryptonewsdesk.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/cryptonewsdesk.com\/#organization","name":"Crypto News","url":"https:\/\/cryptonewsdesk.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/cryptonewsdesk.com\/#\/schema\/logo\/image\/","url":"https:\/\/cryptonewsdesk.com\/wp-content\/uploads\/2025\/04\/Crypto-NEWS.png","contentUrl":"https:\/\/cryptonewsdesk.com\/wp-content\/uploads\/2025\/04\/Crypto-NEWS.png","width":500,"height":500,"caption":"Crypto News"},"image":{"@id":"https:\/\/cryptonewsdesk.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.linkedin.com\/company\/crypto-news-desk"]},{"@type":"Person","@id":"https:\/\/cryptonewsdesk.com\/#\/schema\/person\/56afc0b5a42e13762ccad410f131f96a","name":"Digital Vibe","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/37e93c2e55bfd306b5f3247c0ce7dba6687533106a6330857687e3dcd20fc018?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/37e93c2e55bfd306b5f3247c0ce7dba6687533106a6330857687e3dcd20fc018?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/37e93c2e55bfd306b5f3247c0ce7dba6687533106a6330857687e3dcd20fc018?s=96&d=mm&r=g","caption":"Digital Vibe"},"url":"https:\/\/cryptonewsdesk.com\/index.php\/author\/digital-vibe\/"}]}},"_links":{"self":[{"href":"https:\/\/cryptonewsdesk.com\/index.php\/wp-json\/wp\/v2\/posts\/16001","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cryptonewsdesk.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cryptonewsdesk.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cryptonewsdesk.com\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/cryptonewsdesk.com\/index.php\/wp-json\/wp\/v2\/comments?post=16001"}],"version-history":[{"count":1,"href":"https:\/\/cryptonewsdesk.com\/index.php\/wp-json\/wp\/v2\/posts\/16001\/revisions"}],"predecessor-version":[{"id":16003,"href":"https:\/\/cryptonewsdesk.com\/index.php\/wp-json\/wp\/v2\/posts\/16001\/revisions\/16003"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cryptonewsdesk.com\/index.php\/wp-json\/wp\/v2\/media\/16002"}],"wp:attachment":[{"href":"https:\/\/cryptonewsdesk.com\/index.php\/wp-json\/wp\/v2\/media?parent=16001"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cryptonewsdesk.com\/index.php\/wp-json\/wp\/v2\/categories?post=16001"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cryptonewsdesk.com\/index.php\/wp-json\/wp\/v2\/tags?post=16001"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}