Fact-check findings
What an automated fact-checker found when it re-read Allbridge Core 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.
unverifiable
3 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #4[unverifiable][awaiting moderator]in the summary
“ultimately returned roughly $465,000 of the stolen funds after Allbridge offered a white hat bounty with immunity from legal action.”
reviewerAttacker returned about 1,500 BNB (~$465K) and retained ~$100K as bounty after on-chain offer with immunityRecovery of most funds is corroborated by 2026 retrospectives. The specific figures could not be read in the cited sources. - #5[unverifiable][awaiting moderator]in section: Post-Exploit Security Remediation and Relaunch
“A relaunch update article published May 30, 2023, indicated the team was still finalizing the relaunch at that time.”
reviewerPost-exploit remediation and relaunch; page says team was still finalizing relaunch as of May 30, 2023Medium returned 403 for Allbridge posts. The remediation claims were not verified. - #6[unverifiable][awaiting moderator]in section: ZachXBT Flagging and Community Coverage
“ZachXBT, the pseudonymous on-chain investigator known for tracking DeFi exploits and theft across blockchain networks, flagged the Allbridge Core incident as part of his ongoing monitoring of cross-chain bridge exploits.”
reviewerZachXBT flagged the Allbridge incident via a Twitter postThe page itself admits low-to-medium confidence on a single social reference. No independent support was found.
partially supported
2 claimsThe cited evidence supports part of the claim but not all of it.
- #2[partially supported][awaiting moderator]in section: Attacker Identification and Fund Laundering
“BNB Chain announced via its official account that, thanks to AvengerDAO (a community-driven BNB Chain security initiative), it had identified the perpetrator of the Allbridge exploit through on-chain analysis.”
reviewerBNB Chain and AvengerDAO identified the exploiter via on-chain analysis; BscScan label links to UF Dao hack; exchanges freezing accountsThe identification by BNB Chain is confirmed. AvengerDAO, the UF Dao link and exchange freezes are not in the cited Block article and were not independently checked; other cited sources were blocked or not fetched. - #3[partially supported][awaiting moderator]in the timeline
“2022-07-10”
reviewerKudelski audit completed on 2022-07-10 (timeline), contradicting the December 2022 date used in the page's own proseThe timeline date conflicts with the page's own 'December 2022' statement and with Kudelski's account. The Medium post may have a different publication date, so no correction is proposed. A human should check the post date.
confirmed
1 claimThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in the summary
“On April 1-2, 2023, the protocol suffered a flash loan price-manipulation exploit on BNB Chain that drained approximately $570,000 from its BUSD and USDT liquidity pools.”
reviewerAllbridge Core suffered a flash loan exploit on BNB Chain in April 2023 draining about $570,000Consistent across The Block, Decrypt and CoinDesk retrospectives.