Skip to main content
AVOID.NET
← BurgerSwapreviewed 2026-11-03 · 6 claims checked

Fact-check findings

What an automated fact-checker found when it re-read BurgerSwap 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 3partially supported 2confirmed 10 corrections pending · 0 applied

unverifiable

3 claims

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

  1. #4[unverifiable][awaiting moderator]in section: Post-Exploit Response and Compensation
    “(immediately prior to the exploit on May 27, 2021)”
    reviewerBlock height 7781159 is the snapshot immediately prior to the exploit on May 27, 2021, while the exploit is dated May 28Page elsewhere dates the exploit May 28 (03:00 UTC+8, i.e. May 27 19:00 UTC), so May 27 may be a UTC date; the page does not explain the discrepancy. Block height was not found in any fetched source.
  2. #5[unverifiable][awaiting moderator]in section: Risk Assessment
    “ZachXBT, an established on-chain investigator, has flagged BurgerSwap as a notable entity of concern.”
    reviewerZachXBT flagged BurgerSwap as a notable entity of concernNone of the cited sources and nothing in searches supports this; it has no citation. Recommend removal unless sourced.
  3. #6[unverifiable][awaiting moderator]in section: Rebranding and Subsequent Activity
    “The BURGER token has continued to trade on exchanges including Binance, HTX, and CoinEx following the rebrand.”
    reviewerBURGER continues trading on Binance, HTX and CoinEx after rebrand; no new major incidentsCurrent listing status could not be established, and there are signs of a 2025 token migration proposal and possible delisting that the page does not mention.

partially supported

2 claims

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

  1. #2[partially supported][awaiting moderator]in section: May 2021 Flash Loan and Reentrancy Exploit
    “BURGER's price dropped approximately 27% in the immediate aftermath, falling from $9.24 to $6.75.”
    reviewerBURGER price fell about 27% from $9.24 to $6.75Reports differ (18% in one outlet vs 27% on page); the figure depends on timing and was not confirmed in a fetched source. The arithmetic of $9.24 to $6.75 is internally consistent.
  2. #3[partially supported][awaiting moderator]in section: Root Cause: Removed Security Invariant and Insider Allegations
    “Uniswap founder Hayden Adams publicly commented: 'This thread sounds complicated. Here's what happened very simply. Uniswap v2 fork removed the only line that enforces x*y=k from core,' adding sarcastically 'iWoNDerWhYTHeyDiDtHAt.'”
    reviewerHayden Adams said the Uniswap v2 fork removed the only line enforcing x*y=kSubstance confirmed; verbatim wording not verified. The page's own inference that this implied intent is an interpretation, though it is hedged as unverified.

confirmed

1 claim

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: May 2021 Flash Loan and Reentrancy Exploit
    “On May 28, 2021, at approximately 03:00 UTC+8, BurgerSwap was exploited in a combined flash loan and reentrancy attack spanning 14 transactions, resulting in the theft of approximately $7.2 million in user assets.”
    reviewerExploit drained about $7.2M across 14 transactions via flash loan and reentrancy on May 28, 2021Amount, 14 transactions, date and time are corroborated by The Block and multiple news summaries.
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.