Cork V1 Hack

TOTAL LOST $12.0M
High Access control bypass via hook / Other ethereum

Summarize with AI

Affected Chain ethereum Incident surface
Recovered - No recovery reported
All-Time Rank #278 By amount stolen
Protocol Type Insurance Target category

Incident Overview

On May 28, 2025, Cork Protocol suffered a severe smart contract exploit resulting in the theft of approximately 3,760 wstETH (~$12 million).

The attacker exploited a vulnerability in Cork Protocol’s wstETH:weETH market, taking advantage of faulty exchange rate logic in the smart contract. According to security auditor Dedaub, the exploit was executed by manipulating the exchange rate via fake token issuance, allowing the attacker to mint or withdraw more value than should have been possible. The attack was initiated from a wallet funded by a likely third-party service provider, and the exploited funds — approximately $12M in wstETH — were immediately swapped for ETH.

The malicious contract involved in the attack was deployed just prior to the exploit. Cork Protocol, which has backing from a16z and OrangeDAO, is actively investigating the incident and has paused all other markets to prevent further loss.

Incident Report

Protocol / Project Cork V1
Date of Incident
Affected Chain(s) ethereum
Attack Technique Access control bypass via hook / Other
Classification Protocol Logic / Yield Aggregator
Primary Source View Post-Mortem

Protocol Information

Protocol Type Insurance
Smart Contract Language Solidity
Official Website www.cork.tech/
Protocol Twitter/X @corkprotocol?lang=en
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 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 Cork V1'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? Likely — with a thorough Access control bypass via hook / Other audit checklist and test coverage

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

  • Verify all logic paths related to Access control bypass via hook / Other are guarded by proper access controls and input validation - see the Access Control 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 Access Control Attacks examples →

Sources & References

Learn to Prevent the Next Cork V1

The Cork V1 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