Iron Finance Hack

TOTAL LOST
Other

Summarize with AI

Affected Chain 2021 Incident surface
Recovered - No recovery reported
Same Technique 415 Total incidents
Auditors 2 Prior security audits

Incident Overview

On the 16th of April, TITAN reached an all-time high of $64 and some investors cashed out. As a result, the price dropped to $60, where it remained for a time.

However, when TITAN fell below $60, it prompted a fresh wave of selling by big investors, commonly known as whales, driving the price down below $30. Because of the decline in the TITAN price, the IRON stablecoin lost its peg and fell to $0.90. This is where the real issues started.

The price oracle, which is a smart contract that generates token prices from liquidity pools, could not keep up with the volatility since it utilizes a 10 minute Time Weighted Average Price (TWAP) to determine the CR. Users could purchase IRON tokens for $0.90 and instantly redeem them for $0.75 USDC and $0.25 TITAN, which they could then sell for a risk-free profit.

Investors were ready to purchase dips in IRON and TITAN, helping IRON to briefly reclaim its peg and driving the TITAN price back up to $50.

This triggered another wave of selling as additional major traders began to take advantage of the arbitrage opportunity, flooding the market with newly minted TITAN and finally dumping it as the price approached zero. As a result, IRON fell further, reaching a low of $0.58 before rebounding to $0.74 at the time of writing.

The TITAN supply that was supposed to be capped at 1 billion tokens expanded without limit.

Incident Report

Protocol / Project Iron Finance
Date of Incident
Attack Technique Other
Classification Token

Protocol Information

Protocol Type CDP
Affected Token TITAN
Official Website polygon.iron.finance/
Protocol Twitter/X @ironfinance
Team Anonymous
Source Code Unverified

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 Iron Finance's contract logic - root cause: token
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
Audited by Audit Report 1, Audit Report 2 — still lost —. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to Iron Finance, these are the critical security checks that could have prevented this incident (June 2021).

  • 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

Security Audit History

Sources & References

Learn to Prevent the Next Iron Finance

The Iron Finance 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