Fact-check findings
What an automated fact-checker found when it re-read Echo Protocol against the sources the page cites. Only the most recent review is shown.
These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.
“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.
Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.
disputed
2 claimsThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #9[disputed][awaiting moderator]in the summary
“borrow $3.45 million in WBTC through the Curvance lending protocol”
reviewerThe summary states the attacker 'minted ~$76.7 million and borrow[ed] $3.45 million in WBTC through Curvance.'The page's own section 2 (Exploitation Path) correctly separates the $3.45M eBTC collateral deposit from the ~$867,700 WBTC borrowed, but the summary conflates the two, stating the attacker 'borrow[ed] $3.45 million in WBTC.' This appears to repeat an error present in the CoinDesk article rather than the majority of independently verified reporting.Proposed correction (not yet applied)borrow approximately $867,700 in WBTC through the Curvance lending protocol - #15[disputed][awaiting moderator]in section: Broader DeFi Security Context
“Earlier in May 2026, Drift Protocol and KelpDAO had also reportedly suffered large-scale exploits.”
reviewerEarlier in May 2026, Drift Protocol and KelpDAO had also reportedly suffered large-scale exploits.Multiple independently-fetched and searched sources consistently date the Drift Protocol exploit to April 1, 2026 and the KelpDAO exploit to April 18, 2026 — a full month before the Echo Protocol incident, not 'earlier in May 2026' as the page states.Proposed correction (not yet applied)In April 2026, Drift Protocol and KelpDAO had also reportedly suffered large-scale exploits.
link rot
2 claimsA cited source no longer resolves or no longer says what the page attributes to it.
- #19[link rot][awaiting moderator]in the cited sources
“https://ethnews.com/defis-worst-year-continues-as-76-7m-drained-from-echo-protocol/”
reviewerSource citation: ETHNews article 'DeFi's Worst Year Continues as $76.7M Drained From Echo Protocol' supports the Broader DeFi Security Context section.This source is fully dead (live 410, no Wayback snapshot exists). The underlying factual claim it supported ($76.7M drain, May 2026 exploit wave) remains independently confirmed by other live sources in the same section, so this is a source-hygiene issue rather than a factual dispute. - #20[link rot][awaiting moderator]in the cited sources
“https://web.archive.org/web/20260724220851/https://coinjournal.net/news/bingx-upgrades-bot-trading-infrastructure-to-enhance-futures-strategy-flexiblity/?dynamic”
reviewerSource citation: CoinJournal's ECHO token-plunge article is archived at the given archive_url.The archive_url stored for this source points to a snapshot of a completely different, unrelated CoinJournal article. The live url field is fine and still supports the claim; only the archive_url field is mismatched. No correct archived snapshot was found via the Wayback availability API, so no replacement is proposed — recommend removing the stale archive_url rather than leaving a mismatched one.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #18[partially supported][awaiting moderator]in section: Protocol Background and Audit History
“Hacken, a blockchain security firm, is listed as having conducted at least one audit of Echo Protocol; however, the specific scope, findings, and date of that audit had not been publicly disclosed in detail as of May 2026.”
reviewerHacken conducted at least one audit of Echo Protocol, but the scope, findings, and date were not publicly disclosed in detail as of May 2026.Could not fully load the Hacken audit page directly (403 on fetch); relying on a search snippet that corroborates the page's hedge. Verdict is partially_supported rather than confirmed because independent direct verification of the audit's absence of public detail was incomplete.
confirmed
15 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Admin Key Compromise and Unauthorized Minting
“On May 19, 2026, security firms PeckShield and Lookonchain reported an exploit on Echo Protocol's eBTC contract deployed on the Monad blockchain.”
reviewerOn May 19, 2026, PeckShield and Lookonchain reported an exploit on Echo Protocol's eBTC contract on Monad in which an attacker minted ~1,000 unauthorized eBTC worth ~$76.7 million via a compromised admin key.Core facts confirmed by multiple independently fetched outlets. The Block's more granular timing (flagged evening of May 18 ET) is a timezone artifact the page's own timeline entry for 2026-05-18 already partially captures; not treated as a separate dispute. - #2[confirmed][no action needed]in section: Admin Key Compromise and Unauthorized Minting
“An attacker gained access to an admin-level private key and first assigned themselves the DEFAULT_ADMIN_ROLE on the eBTC smart contract, then granted their wallet the MINTER_ROLE.”
reviewerThe attacker executed a role-escalation sequence, first granting themselves DEFAULT_ADMIN_ROLE then MINTER_ROLE on the eBTC contract, to mint the unauthorized tokens.Confirmed via independent search of Invezz's technical breakdown, which names the same two OpenZeppelin-style roles in the same order. - #3[confirmed][no action needed]in section: Admin Key Compromise and Unauthorized Minting
“Blockchain developer Marioo publicly characterized the failure as "operational, not technical," noting that the eBTC contract itself performed as designed; the attacker abused legitimately structured privileged access.”
reviewerBlockchain developer Marioo characterized the failure as 'operational, not technical,' saying the eBTC contract performed as designed.Quote and attribution confirmed via direct fetch of the cited CoinTelegraph article. - #4[confirmed][no action needed]in section: Admin Key Compromise and Unauthorized Minting
“The on-chain attacker address identified by analysts was 0x6a0109d3c5ab56277096c75e8f5d1d1d45243415.”
reviewerThe on-chain attacker address identified by analysts was 0x6a0109d3c5ab56277096c75e8f5d1d1d45243415.Address matches independently-fetched reporting exactly. - #5[confirmed][no action needed]in section: Exploitation Path and Fund Laundering
“Of the 1,000 minted eBTC, the attacker deposited 45 eBTC (approximately $3.45 million in value) as collateral into Curvance, a decentralized lending protocol that had accepted eBTC as a supported asset.”
reviewerThe attacker deposited 45 eBTC (~$3.45 million) as collateral into Curvance, which had accepted eBTC as a supported asset.Confirmed. - #6[confirmed][no action needed]in section: Exploitation Path and Fund Laundering
“Against this collateral, the attacker borrowed approximately 11.29 wrapped Bitcoin (WBTC), valued at roughly $867,700 at the time.”
reviewerAgainst that collateral, the attacker borrowed approximately 11.29 WBTC (~$867,700).This is the figure independently corroborated by CoinTelegraph, The Block, Decrypt and BeInCrypto. Note this directly contradicts the summary's separate claim that the attacker 'borrowed $3.45 million in WBTC' (see separate finding) — that figure is actually the eBTC collateral value, not the WBTC loan. - #7[confirmed][no action needed]in section: Exploitation Path and Fund Laundering
“approximately 384 to 385 ETH — equivalent to roughly $816,000 to $822,000 — was routed through Tornado Cash, an Ethereum-based privacy mixer, to obfuscate the trail”
reviewerApproximately 384 to 385 ETH (~$816,000-$822,000) was routed through Tornado Cash to obfuscate the trail, with total realized losses estimated at ~$816,000 due to limited Monad liquidity for the remaining eBTC.Page correctly hedges the 384/385 ETH discrepancy across outlets rather than picking one figure. Confirmed. - #8[confirmed][no action needed]in section: Exploitation Path and Fund Laundering
“Curvance paused its eBTC lending market following disclosure, stating that its isolated market architecture prevented contagion to other markets on the platform.”
reviewerCurvance paused its eBTC lending market following disclosure, saying its isolated market architecture prevented contagion to other markets.Confirmed. - #10[confirmed][no action needed]in section: Centralized Access Control Failures
“(1) a single-signature arrangement for the admin role, meaning no multi-signature threshold was required to execute privileged operations; (2) no timelock mechanism governing sensitive administrative actions such as role grants or minting authority changes; (3) no minting supply cap or rate limiter on the eBTC contract, allowing arbitrary quantities to be minted in a single transaction; and (4) insufficient collateral sanity checks on the Curvance integration”
reviewerPost-incident analysis found a single-signature admin role, no timelock, no mint cap/rate limiter, and insufficient Curvance collateral checks.Confirmed; matches independently-fetched Marioo analysis reported by CoinTelegraph. - #11[confirmed][no action needed]in section: Protocol Response and Containment
“The team stated it had successfully regained control of the compromised admin keys and burned the remaining 955 eBTC that had remained in the attacker's possession, preventing their conversion.”
reviewerEcho Protocol confirmed the breach, regained control of admin keys, burned the remaining 955 eBTC, suspended Monad cross-chain functionality, and paused the Aptos bridge as a precaution despite Aptos not being implicated.Confirmed via live-fetched CoinDesk article. - #12[confirmed][no action needed]in section: Protocol Response and Containment
“Monad co-founder Keone Hon publicly confirmed that the Monad network itself was unaffected and continued operating normally, clarifying the exploit was specific to Echo Protocol's application layer.”
reviewerMonad co-founder Keone Hon publicly confirmed that the Monad network itself was unaffected and continued operating normally.Confirmed via independent search corroboration. - #13[confirmed][no action needed]in section: Token Price Impact
“The ECHO native token experienced a decline of over 11% shortly following public disclosure of the security breach on May 19, 2026.”
reviewerThe ECHO native token declined by over 11% shortly after public disclosure of the breach on May 19, 2026.Confirmed via direct fetch of the live CoinJournal article. - #14[confirmed][no action needed]in section: Broader DeFi Security Context
“THORChain experienced a vault breach on May 15, 2026, draining over $10 million in digital assets. Three days later, on May 18, the Verus-Ethereum Bridge was exploited for approximately $11.58 million.”
reviewerTHORChain experienced a vault breach on May 15, 2026, draining over $10 million; the Verus-Ethereum Bridge was exploited for approximately $11.58 million on May 18, 2026; Echo Protocol's exploit brought May 2026's running total of crypto exploits to 14.Dates and figures for THORChain and Verus-Ethereum Bridge, and the '14 exploits in May' running total, are corroborated by independent search results, including the BeInCrypto headline itself. - #16[confirmed][no action needed]in section: Protocol Background and Audit History
“Echo Protocol is a Bitcoin liquidity aggregation and yield infrastructure protocol launched in August 2024, initially focused on the Aptos blockchain before expanding to the Monad network.”
reviewerEcho Protocol launched in August 2024, initially focused on the Aptos blockchain before expanding to Monad; its core product is a wrapped Bitcoin asset (eBTC on Monad, aBTC on Aptos).Confirmed via independent search of Aptos Foundation and IQ.wiki. - #17[confirmed][no action needed]in section: Protocol Background and Audit History
“The protocol secured pre-seed funding in October 2024.”
reviewerEcho Protocol secured pre-seed funding in October 2024.Confirmed, though note the timeline's cited source (CryptoRank) is not listed in the page's sources_used array — a minor sourcing-completeness gap, not a factual error.