Ooki Hack

TOTAL LOST $55.0M
High #118 All-Time Private Key Compromised (Phishing) bsc polygon

Summarize with AI

ChatGPT Perplexity Claude Grok
Affected Chain bsc 2 chains affected
Recovered - No recovery reported
All-Time Rank #118 By amount stolen
Auditors 1 Prior security audit

Incident Overview

Ooki is a flexible decentralized finance protocol for margin trading, borrowing, lending and staking on multiple blockchains.

This is classified as a Phishing Attacks . Compare similar hacks →

Incident Report

Protocol / Project Ooki
Date of Incident
Affected Chain(s) bsc polygon
Attack Technique Private Key Compromised (Phishing)
Classification Infrastructure
Primary Source View Post-Mortem

Protocol Information

Protocol Type Lending
Official Website app.rook.fi/
Protocol Twitter/X @OokiTrade

Market Context at Time of Hack

Token Categories
DeFi Ethereum Ecosystem Yield Farming Three Arrows Capital Portfolio Alameda Research Portfolio Olympus Pro Ecosystem
Protocol Links
Discord Reddit

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 Operational-security tradecraft (phishing, malware, leaked seed phrases, or insider access) to obtain treasury signing authority
Capital Required Minimal capital - only enough to cover gas while draining the compromised accounts
On-Chain Access Valid signing authority over the compromised wallets / multisig signers, allowing direct transfer of funds or stake authorization
Target Reconnaissance Identification of Ooki's high-value treasury accounts and the authority / multisig structure controlling them
Execution Speed Speed to drain the compromised accounts before the team detects the breach and revokes signing authority or freezes the assets
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? Hard to catch — private key / OpSec failures are outside smart contract audit scope
Audited by Audit Report 1 — still lost $55.0M. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • Verify all logic paths related to Private Key Compromised (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

Security Audit History

Related Attack Classes

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

See all Phishing Attacks examples →

Phishing Attacks

Sources & References

Learn to Prevent the Next Ooki

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