Skip to main content
AVOID.NET
← Binance Bridgereviewed 2026-11-02 · 8 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Binance Bridge 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 1partially supported 5confirmed 20 corrections pending · 0 applied

unverifiable

1 claim

No source the reviewer could reach confirms or contradicts the claim.

  1. #8[unverifiable][awaiting moderator]in section: The $586M Exploit
    “The attacker forged proofs claiming to originate from block 110217401”
    reviewerBlock-level and per-transaction details (relayer registration, block 110217401, 18:26 and 20:43 UTC mint times, 44 validators) are attributed to the cited sourcesI did not confirm these details in the sources I fetched. I did not fetch the other cited pages (Immunefi, PT Swarm, Rekt).
    citedrekt.news/bnb-bridge-rekt

partially supported

5 claims

The cited evidence supports part of the claim but not all of it.

  1. #2[partially supported][awaiting moderator]in section: Recovery
    “The Venus Protocol collateral position representing approximately 630,240 BNB remained locked in the DeFi protocol”
    reviewerVenus collateral position of about 630,240 BNB remained locked; the number conflicts with the 900,000 BNB deposit stated earlierThe page gives 900,000 BNB in sections[2] and 630,240 BNB here with no explanation (e.g. a later snapshot or partial repayment). I could not confirm 630,240 from a fetched source, so I propose no correction.
    citedwww.elliptic.co/blog/analysis/attack-min…c-bridge-exploit
  2. #3[partially supported][awaiting moderator]in section: Risk Assessment
    “second only to the Ronin Bridge hack ($624 million, March 2022) in terms of gross value minted”
    reviewerBinance Bridge exploit was second only to Ronin in gross valueFrom general knowledge, the Poly Network hack (August 2021, about $611M) also exceeded the roughly $570-586M figure, so the ranking is probably overstated. I did not fetch a source for this, so I propose no correction.
    citedwww.halborn.com/blog/post/explained-the-…ack-october-2022
  3. #4[partially supported][awaiting moderator]in section: Risk Assessment
    “BNB Smart Chain's 21-validator consensus architecture”
    reviewerBSC consensus architecture is described as 21 validators, while the page elsewhere says all 44 validators halted the chainThe page is internally inconsistent: sections[3] and timeline[6] say 44 validators, while sections[5] says 21. BSC is generally described as having 21 active validators, but I did not fetch a source, so I propose no correction.
    citedwww.halborn.com/blog/post/explained-the-…ack-october-2022
  4. #5[partially supported][awaiting moderator]in section: BSC Chain Halt
    “Approximately 90 minutes after the second minting transaction, BNB Chain validators took coordinated action”
    reviewerHalt came about 90 minutes after the second mintThe page's own times (second mint 20:43 UTC, halt about 21:35 UTC) give about 52 minutes, not 90. I did not independently verify either timestamp.
    citedcointelegraph.com/news/bnb-chain-confirm…otential-exploit
  5. #6[partially supported][awaiting moderator]in the timeline
    “2023-11”
    reviewerVenus governance and forced liquidation occurred in 2023-11Search snippets say Venus governance approved BNB Chain as sole liquidator in November 2022, with staged liquidation in 2023. That conflicts with 'more than a year after the exploit ... proposed'. I could not confirm this from a fetched source, so I propose no correction. The timeline entry has no source.

confirmed

2 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: On-Chain Evidence
    “the attacker deposited approximately 900,000 BNB as collateral on Venus Protocol, a BNB Chain DeFi lending market, and borrowed approximately $147.5 million in stablecoins”
    reviewerAttacker deposited about 900,000 BNB on Venus and borrowed about $147.5M in stablecoinsConsistent with search-snippet reporting, which shows some variation in the BNB amount. The Elliptic page itself was not fetched.
    citedwww.elliptic.co/blog/analysis/attack-min…c-bridge-exploit
  2. #7[confirmed][no action needed]in section: BSC Chain Halt
    “BNB Chain came back online after validators applied a hotfix release (v1.1.15) that patched the IAVL vulnerability.”
    reviewerHotfix v1.1.15 patched the flawThe Halborn page also gives about $566M for the 2M BNB, which is close to the page's $586M. That is a price-basis difference, not an error.
    citedwww.halborn.com/blog/post/explained-the-…ack-october-2022
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.