1Inch Hack

TOTAL LOST $2.6M
Medium Reentrancy

Summarize with AI

Affected Chain 2025 Incident surface
Recovered - No recovery reported
All-Time Rank #586 By amount stolen
Auditors 1 Prior security audit

Incident Overview

On March 6, 2025, 1inch’s Fusion v1 Settlement Contract suffered a $2.6 million exploit, losing approximately $1.2 million in USDC and 638 ETH. The root cause was a re-entrancy vulnerability in the fillOrderInteraction() function, which allowed attackers to repeatedly gain approvals for asset transfers.

The exploited function, fillOrderInteraction(), blindly accepted user-supplied input (takingAmount) and returned that value as the approved transfer amount. This function is part of the 1inch Aggregation Router (0x11111112…960582), which called fillOrderTo(). Critically, both functions accepted arbitrary calldata, opening the door to a re-entrancy attack.

This re-entrancy flaw enabled multiple fraudulent approvals, allowing the attacker to withdraw funds far beyond legitimate order amounts.

Exploit TX Example:

https://etherscan.io/tx/0xb5c94efa…ce1c60

Incident Report

Protocol / Project 1Inch
Date of Incident
Attack Technique Reentrancy
Classification Exchange (DEX)

Protocol Information

Protocol Type DEX Aggregator
Official Website 1inch.io/
Protocol Twitter/X @1inch
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Decentralized Exchange (DEX) Token DeFi Wallet Ethereum Ecosystem AMM YZi Labs Portfolio Avalanche Ecosystem Solana Ecosystem

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 reentrancy 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 1Inch'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? Yes — skilled auditors routinely flag Reentrancy vulnerabilities in code review
Audited by Audit Report 1 — still lost $2.6M. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • Verify all logic paths related to Reentrancy are guarded by proper access controls and input validation - see the Reentrancy attack class for patterns
  • Check that all state-changing functions follow the Checks-Effects-Interactions (CEI) pattern to prevent reentrancy and logic ordering bugs
  • 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

Security Audit History

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Reentrancy examples →

Sources & References

Learn to Prevent the Next 1Inch

The 1Inch 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.

Recreate exploit patterns safely Free Trial