← Taiko Bridge SGX Key Exploit (June 2026)reviewed 2026-10-28 · 9 claims checked
Fact-check findings
What an automated fact-checker found when it re-read Taiko Bridge SGX Key Exploit (June 2026) against the sources the page cites. Only the most recent review is shown.
Read this first
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.
unverifiable
2 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #6[unverifiable][awaiting moderator]in section: Assets Drained and Fund Movement
“Taiko's CEO filed a formal report with Singapore authorities”
reviewerTaiko CEO filed a formal report with Singapore authoritiesThe likely source returned 403, so I could not check it. The claim is also unsourced in the section where it appears (it was placed in the 06-22 containment section, while the timeline dates it June 25). - #9[unverifiable][awaiting moderator]in section: Token and Market Impact
“PeckShield documented $340.7 million in losses across at least 14 bridge exploits during the year as of reporting”
reviewerKelp DAO exploit of about $292M, allegedly by Lazarus, and PeckShield $340.7M across 14 bridge exploitsNot checked within this review's budget. Not scored as confirmed; the Kelp DAO and PeckShield figures should be checked against the BeInCrypto and Chainalysis sources.
partially supported
2 claimsThe cited evidence supports part of the claim but not all of it.
- #4[partially supported][awaiting moderator]in section: Assets Drained and Fund Movement
“1.99 million TAIKO worth about $189,000 (Lookonchain via CoinDesk and CryptoTimes)”
reviewer1.99 million TAIKO worth about $189,000 was reported by Lookonchain via CoinDesk and CryptoTimesCoinDesk gives the $170,000 figure, so it is misattributed to the $189,000 version. The CryptoTimes attribution was not verified (the CryptoTimes 06/22 page was not fetched). - #7[partially supported][awaiting moderator]in section: Detection, Containment and Immediate Response
“a window of roughly eight minutes”
reviewerBlockaid detection and freeze between about 2:00 and 2:08 a.m. ET, roughly eight minutesThe eight-minute figure rests on a tier-3 source (SpotedCrypto). Tier-1 coverage gives a looser timeline, and DARKNAVY places the attack beginning June 21, so describing the response as 'within minutes' in the summary may overstate. Not independently confirmed.
confirmed
5 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in the summary
“Taiko's Ethereum L1 Bridge and ERC20Vault were drained of approximately $1.7 million”
reviewerBridge and ERC20Vault were drained of about $1.7 millionCoinDesk confirms the figure. Blockaid initially estimated over $1M, but Taiko confirmed $1.7M. - #2[confirmed][no action needed]in section: Attack Mechanism and On-Chain Execution
“registered two malicious SGX verifier instances (IDs 5 and 6) in one transaction (0x2f44dc1b883522a88f9b0cbbdfabf9ec33884b69dd4326600c3fab7fb2277260)”
reviewerAttack sequence began June 21 with registration of SGX instances IDs 5 and 6, a 10-call processMessage, checkpoint at block 1805600Page claims line up with the DARKNAVY report, including June 21 start. I did not independently verify the specific state root or the retryMessage description. - #3[confirmed][no action needed]in section: Assets Drained and Fund Movement
“DARKNAVY catalogued the assets drained from the L1 Bridge and ERC20Vault as 675,761.24 USDC, 138,139.56 USDT, 156,832.01 crvUSD and 150.70 ETH/WETH”
reviewerAsset breakdown of drained fundsFigures match. - #5[confirmed][no action needed]in section: Detection, Containment and Immediate Response
“The bridge reopened on July 2, 2026, ten days after the exploit, under conservative withdrawal quotas”
reviewerBridge reopened July 2, 2026 after independent security review, users made wholeConfirmed. The page's statement that no post-mortem was published is as of early July only. - #8[confirmed][no action needed]in section: Recovery, Patch and Bridge Reopening
“CoinDesk reported a slump of more than 20% since midnight UTC”
reviewerTAIKO fell more than 20% per CoinDesk and market cap about $14.5MConfirmed.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.