Ionic Hack

TOTAL LOST $12.3M
High Other

Summarize with AI

ChatGPT Perplexity Claude Grok
Affected Chain 2025 Incident surface
Recovered - No recovery reported
All-Time Rank #281 By amount stolen
Protocol Type Dexs Target category

Incident Overview

Quick Summary

On February 4, 2025, Ionic Protocol suffered a $12.3 million exploit on the Mode network due to social engineering. The attacker deployed a fake Lombard Bitcoin Token (LBTC), manipulated the approval process, and used it as collateral to drain assets. While $3.5 million was bridged to Ethereum and deposited into Tornado Cash, swift action froze $8.8 million on Mode.

Details of the Exploit

The attacker created an imitation LBTC and, through prolonged engagement with the Ionic team, secured its approval as collateral with an API3 Oracle and a Balancer pool. After minting 250 LBTC, they used it to withdraw $12.3 million in supply assets, later depositing them into Layerbank and Ironclad to borrow liquid tokens. Despite Mode freezing the attacker’s wallet, they circumvented the block via Layer 1 transactions, bridging additional assets and depositing another 159 ETH into Tornado Cash.

The Ionic team, alongside SEAL911 and zeroShadow, is working with law enforcement to trace the attacker and recover funds, while a compensation plan is being formulated for affected users.

Incident Report

Protocol / Project Ionic
Date of Incident
Attack Technique Other
Classification Exchange (DEX)
Primary Source View Post-Mortem #1 View Post-Mortem #2

Protocol Information

Protocol Type Dexs
Official Website app.ionic.money/
Protocol Twitter/X @ionicmoney
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
PoS
Protocol Links
GitHub

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Deep understanding of other and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Ionic's contract logic - root cause: exchange (dex)
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Likely — with a thorough Other audit checklist and test coverage

If you're auditing a protocol with similar architecture to Ionic, these are the critical security checks that could have prevented this incident (February 2025).

  • Verify all logic paths related to Other are guarded by proper access controls and input validation
  • Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Sources & References

Browse all hacks

These hacks used the same attack technique. Understanding the pattern helps prevent future exploits.

DeFiTuna $570K
Other
Cascade $1.3M
Other
Lumi Finance $264K
Other
Hinkal $820K
Other
AIDCToken $121K
Other
Polymarket $3.0M
Other

Learn to Prevent the Next Ionic

The Ionic hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Start Free Trial Browse Attack Library
Recreate exploit patterns safely Free Trial