Zaif Hack

TOTAL LOST $59.0M
High #112 All-Time Access Control

Summarize with AI

Affected Chain 2018 Incident surface
Recovered - No recovery reported
All-Time Rank #112 By amount stolen
Protocol Type Exploit/Access control Target category

Incident Overview

Licensed Japanese crypto exchange Zaif was hacked, and 59,000,000 $USD worth of assets was stolen in $BTC, $BCH and MonaCoin

The licensed exchange, called Zaif, is operated by the Tech Bureau. It said on Thursday that the exchange first noticed an unusual outflow of funds on the platform around 17:00 Japan time on September 14, after which the company suspended asset deposit and withdrawal services.

Tech Bureau explained that after further investigation, it discovered that hackers with unauthorized access to the exchange's hot wallets had stolen roughly $60 million in Bitcoin, Bitcoin Cash, and MonaCoin. That being said, the exact amount of bitcoin cash stolen remains unknown.

Tech Bureau said given the nature of the unauthorized fund access, it has filed the incident as a criminal case to local authorities for further investigation.

Incident Report

Protocol / Project Zaif
Date of Incident
Attack Technique Access Control
Classification CeFi

Protocol Information

Protocol Type Exploit/Access control
Official Website zaif.jp/
Protocol Twitter/X @zaifdotjp
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Centralized Exchange (CEX) Token

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 Zaif'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 audit checklist and test coverage

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

  • Verify all logic paths related to Access Control 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 Zaif

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