Legal Notice

Terms of Service & Privacy

By accessing or using Philidor Analytics, the Philidor API, and any other Philidor website, application, or service, you agree to be bound by our Terms of Service and Privacy Policy, including a binding arbitration clause, class-action waiver, and limitation of liability.

Philidor Labs LLC publishes data and analytics only. We are not investment advisers, broker-dealers, commodity trading advisors, transfer agents, or money transmitters.

If you do not agree, please close this tab and do not use the Services.

VaultsProtocolsAssetsEventsOraclesTokenized fundsPortfolio
Philidor AnalyticsPhilidor Analytics
Back to Events
Philidor Analytics

Independent risk infrastructure for on-chain capital.. Real-time, independent vault analytics with open data.

Product

  • Vaults
  • Protocols
  • Assets
  • Oracles
  • Tokenized funds
  • Portfolio

Resources

  • Documentation
  • Methodology
  • FAQ

Legal

  • Privacy Policy
  • Terms of Service
  • Disclaimer

© 2026 Philidor Analytics. All rights reserved.

Data provided for informational purposes only. Not financial advice.

Back to Events
CriticalIncident
Aug 12, 2026

XRP Coreum bridge hack drains 99.7% of reserves in under two hours

XRP
Active

The incident remains unresolved; it stays active until recovery evidence supports closure.

What Happened

On August 9, 2026, the Coreum-XRPL bridge was exploited after relayer software accepted fabricated XRP deposits, creating unbacked balances that were withdrawn against real bridge reserves. First-party and corroborating reports estimate approximately $200,000 of XRP was removed—99.7% of the bridge reserve—in under two hours. No canonical incident transaction hash was included in the preserved sources.

Impact

Loss Amount$200.00K
Affected AssetXRP
Incident CategoryBridge Validation Exploit
NetworksCoreum · XRP Ledger
Reported reserve loss99.7%
Scopeprotocol
Incident Severitymajor
ResolutionUnresolved

On-Chain References

No canonical incident transaction was disclosed in the preserved sources. Philidor does not substitute an unrelated contract or wallet transaction.

Resources

Official TX Ecosystem incident noticeTechnical incident analysisSource reportIndependent reportIndependent report

Provenance & Methodology

Producercryptominute-news
Verificationissuer and multi source reported

Source-backed incident record anchored to a preserved first-party issuer disclosure. Philidor applies its own severity policy but does not infer an undisclosed loss amount or transaction.

Timeline

Reported incident dateAug 9, 2026
Source report publishedAug 12, 2026, 3:41 PM
DetectedAug 13, 2026, 10:35 PM
RecordedAug 13, 2026, 10:35 PM