Fact-check findings
What an automated fact-checker found when it re-read Badger DAO 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.
- #2[unverifiable][awaiting moderator]in section: The Frontend Attack
“Beginning November 10, 2021, the attacker used the unauthorized API key to inject malicious JavaScript via Cloudflare Workers into specific routes of the Badger web application.”
reviewerThe exploit affected approximately 500 wallets and the attacker began injecting on Nov 10, 2021 with first approval Nov 20, 2021The primary cited CoinDesk piece does not contain these dates or the ~500 wallet count. They likely come from Badger's post-mortem or other cited sources, which I did not reach in this pass. - #4[unverifiable][awaiting moderator]in the timeline
“BadgerDAO Treasury Council announces sunset of the eBTC protocol, citing failure to achieve product-market fit and insufficient TVL to sustain revenue.”
reviewerBadgerDAO Treasury Council announced sunset of eBTC on 2025-06-11 citing failure to achieve product-market fitSeveral searches found no source for the specific date, the Treasury Council attribution, or the stated reasons. The timeline entry also has no source. Also affects the summary and Risk Assessment statements. - #5[unverifiable][awaiting moderator]in section: Risk Assessment
“The eBTC protocol, BadgerDAO's next major product, was sunset by the Treasury Council in June 2025 after failing to achieve product-market fit.”
reviewereBTC was sunset in June 2025 (Risk Assessment)Same unsupported claim as the timeline entry; no fetched source confirms it.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #7[partially supported][awaiting moderator]in the summary
“total value locked has fallen to low single-digit millions”
reviewerTotal value locked has fallen to low single-digit millions as of 2025TVL has been far below its peak, but current figures (~$12.9M) are not 'low single-digit millions'; only a brief low in early 2026 was. Body text elsewhere says $9-10M by 2023, which is inconsistent with the summary.
confirmed
3 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: The Frontend Attack
“On December 2, 2021, BadgerDAO suffered one of the largest DeFi exploits in history”
reviewerOn December 2, 2021 BadgerDAO suffered a front-end attack draining roughly $120-130 million via a compromised Cloudflare API keyDate, amount range, vector and the ~$9M recoverable figure match CoinDesk. - #3[confirmed][no action needed]in section: Recovery Efforts
“A subsequent investigation revealed that an error in Celsius's claims process during the BadgerDAO restitution resulted in Celsius forfeiting approximately $22 million in recovery entitlements due to administrative failures on Celsius's part, according to reporting by Dirty Bubble Media.”
reviewerCelsius forfeited approximately $22 million of BadgerDAO restitution entitlements due to an administrative error, per Dirty Bubble MediaFigure and attribution match. Source describes the cause as Celsius withdrawing remBadger, which the page's 'administrative failures' wording summarizes loosely. - #6[confirmed][no action needed]in the timeline
“Binance delists BADGER following a community vote-to-delist, citing low trading volume and development activity.”
reviewerBinance delisted BADGER on April 16, 2025 following a community voteDate confirmed from the TradingView/Coindar headline; the stated reasons were not independently read.