Bunni V2 Exploit $8.3M Drained via Liquidity Flaw #1381
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
Bunni V2 Exploit Technical Summary
Incident — September 2, 2025
Bunni V2, a
Uniswap v4
hook–based protocol, was exploited for approximately $8.3M total ($2.4M on Ethereum and $5.9M on UniChain). The attacker abused a precision/rounding bug inBunniHook
’sLiquidity Distribution Function (LDF)
that mis-accounted liquidity during swap-triggered rebalancing, allowing withd...🔧 Technical Details
Threshold‑crossing precision abuse in DEX hooks: When a DEX integrates a custom rebalancing function (e.g., an LDF in a Uniswap v4 hook), craft exact‑input swaps calibrated to cross internal rebalancing thresholds. Precision/rounding errors in the hook’s accounting can accumulate as positive credits rather than cancel out. Loop swaps to build the credit, then withdraw the inflated balance to realize the gain.
Flash‑loan amplification and exit: Use large flash loans to run many threshold‑crossing swaps in one atomic transaction, ensuring loan repayment from the inflated withdrawal. Where the hook is deployed on multiple chains, repeat the pattern cross‑chain and bridge proceeds back. Optionally route funds through lending protocols (e.g., Aave) to obtain synthetic assets.
🤖 Agent Actions
Analysis and plan:
What I added:
Why this is the right place:
Repository changes performed:
References included in the new page:
No redundant content added:
If you want me to add more case studies or include concrete calldata/tx flows for the known transactions, I can extend the page further.
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.
🗑️ File Cleanup