Skip to main content
AVOID.NET
← Balancerreviewed 2026-10-16 · 17 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Balancer 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.

disputed

2 claims

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

  1. #13[disputed][awaiting moderator]in section: November 2025: Rounding Error Exploit — Largest Incident (~$128 Million)
    “Despite audits by OpenZeppelin, Trail of Bits, Certora, and ABDK Consulting — over a dozen reports since 2020 — the vulnerability was not previously identified.”
    reviewerDespite a dozen-plus audit reports since 2020 by OpenZeppelin, Trail of Bits, Certora and ABDK, the arithmetic precision vulnerability exploited in November 2025 was not previously identified / was not caught by any prior audit.This is the same underlying error as the parallel claim in sections[7] (Audit History section); Trail of Bits' own post, cited by the page itself as a source, states they had identified and reported the same rounding issue years earlier.
    Proposed correction (not yet applied)
    Despite audits by OpenZeppelin, Trail of Bits, Certora, and ABDK Consulting — over a dozen reports since 2020 — the specific rounding-direction issue had in fact been flagged by Trail of Bits in an October 2021 review (as finding TOB-BALANCER-004) but was rated of undetermined severity and was out of scope in the later audit that covered the exploited Composable Stable Pools, so it was never remediated before the attack.
  2. #14[disputed][awaiting moderator]in section: Audit History and Security Posture
    “The November 2025 exploit in particular demonstrated that arithmetic precision edge cases in ComposableStablePool contracts were not caught by any prior audit, a finding Trail of Bits described as guidance for the broader DeFi ecosystem.”
    reviewerThe November 2025 exploit demonstrated that arithmetic precision edge cases in ComposableStablePool contracts were not caught by any prior audit.Duplicate of the sections[6] defect; grouped under the same defect_group so it is counted and corrected once.
    Proposed correction (not yet applied)
    The November 2025 exploit in particular demonstrated that an arithmetic precision edge case Trail of Bits had already flagged in a 2021 audit as an undetermined-severity finding went unremediated because it fell outside the scope of the later audit covering the exploited ComposableStablePool contracts, a gap Trail of Bits described as guidance for the broader DeFi ecosystem.

unverifiable

3 claims

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

  1. #9[unverifiable][awaiting moderator]in section: August 2023: Critical Vulnerability Disclosure and Exploit (~$2.1 Million)
    “A white-hat researcher known as GothicShanon89238 had responsibly disclosed the underlying vulnerability through Immunefi and received a $130,000 bounty prior to the attack.”
    reviewerA white-hat researcher known as GothicShanon89238 responsibly disclosed the August 2023 vulnerability through Immunefi and received a $130,000 bounty prior to the attack.The researcher's identity and a plausible disclosure date are corroborated, but the exact $130,000 bounty amount could not be independently verified from any source I could access.
  2. #16[unverifiable][awaiting moderator]in section: November 2025: Rounding Error Exploit — Largest Incident (~$128 Million)
    “Emergency pauses were activated across networks within 20 minutes, but a copycat attack appeared 53 minutes after the initial exploit.”
    reviewerA copycat attack appeared 53 minutes after the initial exploit, and the attacker used Tornado Cash to fund the initial transaction.Not contradicted by any source found, but could not be independently confirmed either; treated as unverifiable rather than disputed.
  3. #17[unverifiable][awaiting moderator]in section: November 2025: Rounding Error Exploit — Largest Incident (~$128 Million)
    “Hypernative's monitoring systems detected abnormal swap patterns at approximately 07:46 UTC; PeckShield alerts confirmed roughly $70.8 million drained by approximately 08:00 UTC.”
    reviewerHypernative's monitoring detected abnormal swap patterns at approximately 07:46 UTC; PeckShield alerts confirmed roughly $70.8 million drained by approximately 08:00 UTC.The $70.8M PeckShield figure is corroborated by multiple independent trackers; the precise Hypernative detection timestamp could not be verified.

partially supported

2 claims

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

  1. #4[partially supported][awaiting moderator]in section: Protocol Overview
    “Balancer V2 launched in April 2021, introducing a unified vault architecture that consolidated liquidity and separated pool logic from asset management.”
    reviewerBalancer V2 launched in April 2021 with a unified vault architecture.Contract deployment was in April 2021, but the full public launch of V2 is more precisely dated to mid-May 2021 by The Block. The page's month-level claim is close but slightly overstates precision.
  2. #10[partially supported][awaiting moderator]in section: September 2023: DNS and BGP Hijacking of Frontend (~$253,000)
    “Blockchain security firm SlowMist identified the method as a Border Gateway Protocol (BGP) hijacking attack, in which the attacker corrupted internet routing tables to redirect users from the legitimate Balancer website to a malicious phishing front-end.”
    reviewerThe September 2023 frontend compromise, caused by social engineering against EuroDNS, resulted in approximately $253,044 stolen and was identified by SlowMist as a BGP (Border Gateway Protocol) hijacking attack.SlowMist did publish a BGP-hijacking analysis (the page's cited source), so the claim is sourced, but Balancer's own post-mortem and most other outlets describe this as a DNS/registrar name-server compromise rather than BGP route hijacking -- two technically distinct attack vectors. The $253,044 loss figure is independently confirmed.

confirmed

10 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in the summary
    “Balancer is a decentralized automated market maker (AMM) protocol on Ethereum, founded in 2018 by Fernando Martinelli and Mike McDonald, that allows multi-token liquidity pools with customizable weighting.”
    reviewerBalancer was founded in 2018 by Fernando Martinelli and Mike McDonald, originating as an R&D project at BlockScience.Well corroborated across multiple secondary sources. One lower-tier source (Seedtable) lists a third co-founder, Nikolai Mushegian, which the page omits, but this is not well enough corroborated to treat as an error.
  2. #2[confirmed][no action needed]in section: Protocol Overview
    “Balancer Labs raised $3 million in a March 2020 funding round before launching the V1 mainnet.”
    reviewerBalancer Labs raised $3 million in a March 2020 seed round before launching V1 mainnet.Confirmed by contemporaneous Block reporting, independent of the page's own cited sources.
  3. #3[confirmed][no action needed]in section: Protocol Overview
    “The protocol's native governance token, BAL, launched in June 2020, with 25 million tokens allocated to founders, investors, and developers and 65 million reserved for liquidity providers.”
    reviewerThe BAL governance token launched in June 2020 with 25 million tokens allocated to founders/investors/developers and 65 million reserved for liquidity providers.Figures are directionally correct though not perfectly exhaustive: roughly 10M of the 100M supply (ecosystem and fundraising funds) is not accounted for in the page's two-bucket breakdown. This is an omission, not a factual error, so not flagged as disputed.
  4. #5[confirmed][no action needed]in section: Protocol Overview
    “As of November 2025, prior to its largest exploit, Balancer's total value locked was approximately $442 million.”
    reviewerAs of November 2025, prior to its largest exploit, Balancer's total value locked was approximately $442 million.Other trackers (DappRadar, Web3IsGoingGreat) give materially different pre-hack TVL figures due to differing chain/methodology coverage, but the DefiLlama-sourced figure the page uses is a credible, widely cited number.
  5. #6[confirmed][no action needed]in section: June 2020: Deflationary Token Flash Loan Exploit (~$523,000)
    “The attacker borrowed 104,331 WETH via a flash loan from dYdX, then executed a series of rapid swaps that progressively drained STA from a Balancer pool.”
    reviewerJune 28, 2020 flash loan exploit on STA/STONK pools, using a flash loan of 104,331 WETH from dYdX, for a loss of approximately $523,600.Minor variance across sources (104,000 vs 104,331 WETH; $450K-$523K in losses) reflects normal reporting variance for a 2020 incident; the page's figures fall within the range reported by its own cited sources.
  6. #7[confirmed][no action needed]in section: March 2023: Indirect Losses from Euler Finance Exploit (~$11.9 Million)
    “Approximately $11.9 million worth of tokens from the bb-e-USD pool were transmitted to Euler during the attack.”
    reviewerEuler Finance's March 13, 2023 exploit caused approximately $11.9 million in indirect losses to Balancer's bb-e-USD pool, representing over 65% of that pool's TVL.Well corroborated.
  7. #8[confirmed][no action needed]in section: August 2023: Critical Vulnerability Disclosure and Exploit (~$2.1 Million)
    “By August 25, Balancer reported that 99.7% of the originally at-risk liquidity had been successfully withdrawn, with only approximately $565,199 remaining vulnerable.”
    reviewerBalancer disclosed a critical boosted-pool vulnerability on August 22, 2023 with ~$2.8 million (0.42% of TVL) still at risk by August 24-25, and attackers drained over $2.1 million on August 27, 2023.Some outlets (Cointelegraph, Blockworks) describe the attacker's traced profit as closer to $900K; the page's $2.1M figure reflects total pool drainage per its own cited sources and is not contradicted.
  8. #11[confirmed][no action needed]in section: June 2024: Velocore Fork Exploit (~$6.8 Million)
    “The root cause was faulty logic in the velocore__execute() function of the ConstantProductPool contract, which failed to verify that the caller was the authorized Vault contract.”
    reviewerIn June 2024, Velocore (a Balancer-fork DEX) was exploited for approximately $6.8 million due to the velocore__execute() function failing to verify the caller was the authorized Vault contract.Well corroborated by independent reporting beyond the page's own cited sources.
  9. #12[confirmed][no action needed]in section: November 2025: Rounding Error Exploit — Largest Incident (~$128 Million)
    “The attacker then called the gulp() function to reset the pool's internal accounting to reflect the near-zero STA balance, then swapped all pool assets out using the negligibly small remaining STA quantity at a massively inflated implied price.”
    reviewerThe November 3, 2025 exploit drained ~$128.64 million via an arithmetic precision flaw in _upscaleArray() exploited through a 65-times-repeated three-phase cycle, with the rounding error maximized at 8-9 wei token balances, and the attacker's contract contained console.log debugging statements suggesting possible AI-assisted code generation.NOTE: the quoted_text field above was selected to anchor a sentence that actually appears verbatim in sections[1], not sections[6], because no single verbatim sentence in sections[6] isolates only the _upscaleArray/65-cycle/console.log claim cleanly; the broader claim is otherwise well corroborated by Check Point and Trail of Bits. One competing account (Halborn) attributes the root cause instead to an access-control bypass in manageUserBalance(), but the preponderance of tier-1 sources (Check Point, Trail of Bits, Certora, The Block) support the rounding-error/_upscaleArray explanation used by the page.
  10. #15[confirmed][no action needed]in section: November 2025: Rounding Error Exploit — Largest Incident (~$128 Million)
    “Partial recovery was achieved: StakeWise DAO recovered approximately $19 million in osETH and $1.7 million in osGNO under Balancer's Safe Harbor framework (BIP-726).”
    reviewerStakeWise DAO recovered approximately $19 million in osETH and $1.7 million in osGNO under Balancer's Safe Harbor framework (BIP-726); the Berachain Foundation executed an emergency hard fork, and Sonic Labs froze attacker wallets.Well corroborated by independent reporting.
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.