Azuki Hack

TOTAL LOST $750K
Low Phishing

Summarize with AI

Affected Chain 2023 Incident surface
Recovered - No recovery reported
All-Time Rank #901 By amount stolen
Protocol Type DePIN Target category

Incident Overview

The Azuki Twitter @AzukiOfficial was compromised and brought a loss of up to 750,000 $USD.

The Azuki Twitter account was abruptly taken over, and a scam drained over $750,000 worth of USDC, 11 NFTs, and over 3.9 ETH in less than 30 minutes. The scam used malicious links posing as a "land mint" for the Azuki NFT project to trick users into signing transactions that drained assets from their wallets. The Azuki Twitter account was deleted, and the official account removed from Twitter search results within an hour.

The Azuki team confirmed that the account had been compromised and is working to regain control. The NFT collection has been targeted by scammers before.

Incident Report

Protocol / Project Azuki
Date of Incident
Attack Technique Phishing
Classification NFT

Protocol Information

Protocol Type DePIN
Official Website dokidoki.finance/
Protocol Twitter/X @Azuki
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Collectibles & NFTs DeFi Ethereum Ecosystem Yield Farming Polygon Ecosystem

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 Azuki's contract logic - root cause: nft
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 Azuki, these are the critical security checks that could have prevented this incident (January 2023).

  • 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 Azuki

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