Skip to content
HelpfulCoin

Security and scams · Explainer

What Happened in the Balancer Exploit of November 2025?

Balancer suffered a major exploit on November 3, 2025, involving a precision-loss bug in Balancer v2 composable stable pools. Learn what happened, what is and is not known about its impact, and how to check your exposure safely.

By the HelpfulCoin editorial team · Updated

Illustration for What Happened in the Balancer Exploit of November 2025?

What happened in the Balancer exploit?

The Balancer exploit was a November 3, 2025 attack on Balancer v2 that used a precision-loss bug to drain liquidity from connected pools. Reports estimate the loss at more than $100 million, with one estimate putting it at about $128 million. The attack drew attention to the risks of complex DeFi contracts, especially when pools share infrastructure.

Balancer is a decentralized exchange and liquidity protocol. Its pools hold token reserves that users can trade against or deposit into. The reported attack involved composable stable pools, which are designed to support swaps between assets intended to track similar values.

The reported vulnerability was in a function called _upscaleArray. An attacker combined its rounding behavior with carefully crafted batch swaps. A rounding error is a small discrepancy caused when a contract has to represent calculations using limited numerical precision. Repeated or strategically arranged operations can sometimes make a tiny discrepancy matter.

The incident was not described as a theft of users’ passwords or seed phrases. It was an on-chain contract exploit: the attacker manipulated protocol logic to remove assets held by pools.

How did the attacker exploit Balancer v2?

Reports attribute the exploit to precision loss in Balancer v2’s _upscaleArray function, used during batch swaps involving composable stable pools. A batch swap lets a trader combine multiple token exchanges into one transaction. The vulnerable calculation could round values in a way that an attacker could exploit through carefully constructed operations.

A simplified explanation is that a pool’s accounting and its actual token balances must stay aligned. If a calculation repeatedly rounds in the wrong direction, the contract may treat a pool’s balance differently from its true economic value. The attacker’s transactions took advantage of that discrepancy to extract assets.

The risk was amplified by Balancer’s interconnected pools and shared vault logic. A vault is a contract that holds or accounts for pool assets. When several pools depend on the same core infrastructure, a weakness in that infrastructure can affect more than one pool. That does not mean every pool was necessarily affected in the same way; exposure depends on the contracts and assets involved.

The details above describe the reported mechanism, not a transaction recipe. Recreating exploit steps is unsafe and unnecessary for users trying to protect their funds.

Which Balancer pools and users were affected?

The reported incident affected Balancer v2 composable stable pools, with losses spreading across connected pools that relied on shared vault logic. The summaries of the attack do not provide a complete pool-by-pool list or a definitive exposure total for every token.

If you deposited into Balancer, do not assume that all of your assets were affected—or that your pool was unaffected—based only on the overall loss estimate. Exposure can depend on the exact pool, contract version, network, token and timing of your position. A pool’s current balance may also fail to show whether a past loss affected its users.

To investigate a position:

  1. Identify the pool and network where you deposited, using your wallet or transaction records.
  2. Check Balancer’s current incident updates for notices about that specific pool or contract.
  3. Compare those details with your own on-chain position and transaction history.
  4. If a notice is unclear, avoid interacting with the pool until you understand what it means.

A general exploit headline or a token’s price movement is not enough to establish whether an individual deposit was affected.

Were the stolen funds recovered, and is the issue fixed?

A precise current recovery total is not given by the reported loss estimates. They describe the scale of the exploit, not how much may later have been recovered, returned or made available to affected users.

The attack summaries also do not settle the current pool-by-pool status or the full remediation history. Those details can change after an incident, so check Balancer’s current official incident updates before deciding whether to withdraw, claim anything or use a pool again. Do not treat an old report, social post or token price as proof that a particular contract is repaired.

A practical way to read an incident update is to look for:

  • The exact affected pool addresses, networks and contract versions.
  • Whether Balancer says deposits, swaps or withdrawals are paused or safe.
  • Any announced recovery process and the conditions for participation.
  • Whether a fix has been deployed and which contracts it covers.

If no current, specific statement answers a question about your position, treat that uncertainty as a reason to pause rather than as evidence that funds are safe.

What should Balancer users do after the exploit?

Start by checking your own position and relying on current, pool-specific incident information before taking action. A contract exploit does not automatically mean that every Balancer user lost funds, but interacting with the wrong contract or a fake recovery offer can create additional losses.

Use this checklist:

  1. Open your wallet directly and identify any Balancer pool positions and approvals. Do not follow a message claiming to show your exposure.
  2. Match the pool and network against Balancer’s official incident updates. Confirm contract addresses using trusted records you already use, not unsolicited links.
  3. If the pool is identified as affected or its status is unclear, avoid adding funds or making swaps until Balancer gives specific guidance.
  4. Review token approvals. Revoke approvals you no longer need using your wallet’s established security process, and check each transaction before signing.
  5. Keep your seed phrase and private keys offline. No legitimate recovery process needs them.
  6. Save transaction records and seek qualified help if the position is substantial or the recovery instructions are difficult to verify.

Do not rush to move assets just because an account or message claims there is an urgent deadline.

Is Balancer safe to use after the November 2025 hack?

Yes, using Balancer after an exploit can still involve substantial smart-contract risk. A fix to one vulnerability would not make every pool, contract or future interaction risk-free, and a past incident does not by itself prove that all current Balancer contracts remain vulnerable.

Before using a pool, check which version and network it uses, whether Balancer has issued an update about that specific contract, and whether the action is a swap, deposit or withdrawal. These actions have different risks. A swap can fail or execute at an unfavorable rate; a liquidity deposit can expose assets to pool imbalances, contract bugs and token-specific risks.

Do not rely on a token’s listing, a pool’s apparent popularity or a security review as a guarantee. Audits and reviews can identify some problems but cannot prove that software is free of vulnerabilities. Also remember that a pool’s displayed value or yield is not a promise that assets can be withdrawn at the same value.

If the pool’s current status or the contract address cannot be verified, waiting is safer than signing a transaction you do not understand.

What mistakes should users avoid after the Balancer hack?

The most common mistakes are trusting urgency, confusing a pool-level exploit with a wallet breach, and treating an old incident report as current security guidance. Scammers often use high-profile attacks to impersonate teams and offer fake refunds or recovery claims.

Watch out for:

  • Fake recovery links: Do not connect a wallet or sign a message from an unsolicited claim that promises reimbursement.
  • Seed phrase requests: Never enter a seed phrase or private key into a website, form or chat, even if it appears to be an official support channel.
  • Unverified contract addresses: A lookalike pool or token can use a similar name. Verify the exact network and address before approving a transaction.
  • Blind approval signing: Read what a wallet transaction authorizes. An approval may let a contract move tokens later, not just complete the current swap.
  • Assuming every pool is affected—or safe: The incident involved particular Balancer v2 logic and connected pools; individual exposure requires pool-specific checks.
  • Rushing to withdraw: A hurried transaction can interact with the wrong contract or incur avoidable risks. Follow current, specific instructions rather than social-media pressure.

What does the Balancer exploit mean for DeFi users?

The main lesson is that DeFi risk can arise from small arithmetic errors in widely used contract logic, not only from obvious wallet theft or a broken password. Balancer’s November 2025 exploit involved precision loss in a calculation, carefully arranged batch swaps and interconnected pool infrastructure.

For users, the practical takeaways are straightforward: identify the exact pool and contract behind a position, check current incident notices, and treat unverified recovery claims as suspicious. Do not assume that a protocol’s overall reputation or an audit makes every interaction safe. If a pool’s status is unclear, avoid new deposits and transactions until the risk is explained.

For anyone comparing decentralized exchanges, remember that every protocol has its own contracts and failure modes. Moving funds to another exchange or protocol does not remove smart-contract, token, market or wallet risks. It simply changes which risks apply.

Balancer’s reported loss estimates establish that the event was serious, but they do not by themselves answer whether a particular user’s funds were affected or what recovery may have occurred. Those questions require current, specific information about the pool and the user’s position.

Frequently asked questions

When was the Balancer exploit, and how much was lost?

The attack was reported on November 3, 2025. Reports estimate losses at more than $100 million, with one estimate reaching about $128 million.

What caused the Balancer exploit?

Reports describe a precision-loss bug in Balancer v2’s _upscaleArray function, used with carefully crafted batch swaps. The issue affected composable stable pools and allowed the attacker to drain liquidity across connected pools.

Were users’ wallets hacked?

It was a smart-contract exploit, not a reported breach of users’ wallets or seed phrases. However, anyone whose assets were in affected pools may have faced losses, so check the specific pool and token exposure.

Is Balancer safe to use after the 2025 exploit?

No. A past exploit does not prove that every Balancer contract is vulnerable, but it does show that pool and contract risks can be significant. Check Balancer’s current incident updates and the specific contracts involved before interacting.

Were the stolen funds recovered?

No precise current recovery total is given by the reported loss estimates. Do not assume funds were recovered or that a particular pool is safe without a current update from Balancer.

Mentioned in this guide

dApps in this guide

Score 3.8 out of 10

Balancer is an Ethereum DEX and liquidity protocol, but its reported 2025 attack makes its current contract risks a serious concern.

Ethereum
Match logo

Match

Infrastructure

Score 5.5 out of 10

Match-Trader is trading software for brokers and prop firms; traders should check the provider behind their account before depositing.

Save logo

Save

Lending

Score 5.8 out of 10

Save is a lending protocol on Solana and Eclipse; it offers crypto lending and borrowing, but carries smart-contract and collateral risks.

TVL $58.8M−14.5%Solana · Eclipse
Seed logo

Seed

Other

Score 6.0 out of 10

Seed is a supplement company selling DS-01 synbiotic; its price and unguaranteed health claims merit a careful check.

Keep reading

Related guides

All security and scams guides

NFT · Explainer

What Are Omnimorphs and Quadrums NFT Rankings?

“Omnimorphs,” “Quadrums” and “Storm rankings” do not, by themselves, identify a verifiable NFT collection or ranking page. Learn how to check the exact collection, interpret rankings and reduce the risks before connecting a wallet or buying.

DeFi · Review

Is Balancer Safe to Use in 2026?

Balancer is a decentralized exchange and liquidity protocol built around configurable token pools. Its flexible design may suit experienced DeFi users, but a reported 2025 attack makes checking current contract and incident information essential before using it.

Security and scams · Explainer

Did Crypto Rug Pulls Cost More Than Ever in 2025?

A 2025 estimate put crypto rug-pull losses near $6 billion, largely because it counted the Mantra Network case, while another figure reported fewer incidents. That makes “costing more than ever” hard to verify: totals depend on what gets classed as a rug pull, and one large case can dominate the yearly sum.

Security and scams · Explainer

What Happened in the BadgerDAO Hack?

In December 2021, attackers drained roughly $120 million in crypto from wallets interacting with BadgerDAO. The incident showed how a compromised website can put wallet funds at risk even when the underlying blockchain is working normally.

Security and scams · Explainer

What Happened in the Azuki Founder Controversy?

Azuki’s founder disclosed a history of earlier NFT projects that were abandoned, prompting backlash in 2022. Here’s why people called it a rug pull, what the disclosure did—and didn’t—prove, and how NFT holders can protect themselves.