Ribbon Finance Hack

TOTAL LOST $351K
Low Phishing

Summarize with AI

Affected Chain 2022 Incident surface
Recovered - No recovery reported
All-Time Rank #1103 By amount stolen
Protocol Type Farm Target category

Incident Overview

A DNS attack was made on Ribbon Finance. During the attack one of the users lost 16.5 $WBTC.

A DNS attack was carried out on the Ribbon Finance project, during which 16.5 $WBTC was lost. The on-chain analysis revealed that the attack has common features with the DNS attack on Convex Finance and was made by the same hacker team. Hackers created a similar website with a malicious contract that required calling the approve() function.

Scammer address: https://etherscan.io/address/0xb7326148…5af9aa

Contract creator address: https://etherscan.io/address/0x47832f55…146fc6

Malicious contract address: https://etherscan.io/address/0x65a8ec2c…453b2f

Transferring 16.5 $WBTC from "victim" to scammer address transaction: https://etherscan.io/tx/0xd09057f1…510850

Incident Report

Protocol / Project Ribbon Finance
Date of Incident
Attack Technique Phishing
Classification Yield Aggregator

Protocol Information

Protocol Type Farm
Affected Token RBN
Official Website app.ribbon.finance/
Protocol Twitter/X @ribbonfinance
Team Anonymous
Source Code Verified On-Chain

Market Context at Time of Hack

Token Categories
DeFi Derivatives Ethereum Ecosystem Coinbase Ventures Portfolio Real World Assets Protocols

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 phishing 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 Ribbon Finance's contract logic - root cause: yield aggregator
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 Phishing audit checklist and test coverage

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

  • Verify all logic paths related to Phishing are guarded by proper access controls and input validation - see the Phishing Attacks attack class for patterns
  • 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

Related Attack Classes

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

See all Phishing Attacks examples →

Sources & References

Learn to Prevent the Next Ribbon Finance

The Ribbon 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