Unizen Hack

TOTAL LOST $2.1M
Medium External Call Vulnerability / Other ethereum

Summarize with AI

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

Incident Overview

DeFi protocol Unizen suffered a $2.1 million exploit, prompting the immediate reimbursement of affected users. The exploit involved a compromised platform and the draining of user funds, leading to significant financial losses.

On March 9th, blockchain analytics firm PeckShield identified an "approve issue" with Unizen, resulting in over $2 million being drained from the platform. The attacker exchanged Tether (USDT) for Dai (DAI), causing substantial losses. Unizen quickly initiated bounty negotiations with the hacker and began collaborating with law enforcement and forensic experts to identify the perpetrator.

Despite ongoing negotiations, Unizen promptly refunded 99% of affected users, with refunds starting on March 11th. CEO Sean Noga loaned funds to facilitate the reimbursement process, with users who lost below $750,000 receiving refunds in USDT or USD Coin (USDC).

Vulnerable contract created:

https://etherscan.io/tx/0x858c7187…43ef59

Incident Report

Protocol / Project Unizen
Date of Incident
Affected Chain(s) ethereum
Attack Technique External Call Vulnerability / Other
Classification Protocol Logic / Exchange (DEX)
Primary Source View Post-Mortem

Protocol Information

Protocol Type DEX Aggregator
Smart Contract Language Solidity
Official Website www.unizen.io/
Protocol Twitter/X @unizen_io
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Ethereum Ecosystem Exnetwork Capital Portfolio Polygon Ecosystem BNB Chain Ecosystem DWF Labs Portfolio

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 external call vulnerability / other and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with ethereum smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Unizen's contract logic - root cause: protocol logic / 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? Likely — with a thorough External Call Vulnerability / Other audit checklist and test coverage

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

  • Verify all logic paths related to External Call Vulnerability / Other are guarded by proper access controls and input validation - see the Delegatecall & Call Injection 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 Delegatecall & Call Injection Attacks examples →

Proof-of-Concept Exploits

1 PoC available

Sources & References

Learn to Prevent the Next Unizen

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