Zerogoki Hack

TOTAL LOST $670K
Low Other

Summarize with AI

Affected Chain 2021 Incident surface
Recovered - No recovery reported
All-Time Rank #930 By amount stolen
Protocol Type Exploit/Other Target category

Incident Overview

Zerogoki was attacked by way of compromising the price oracle. The attacker provided a price oracle signed by legitimate private keys, which contained a crafted number of tokens to be swapped. However, the reason why the attacker could construct a valid signature is unknown.

The attacker's address:

https://etherscan.io/address/0xaef46df5…30680d

The transaction behind the attack:

https://etherscan.io/tx/0x81e5f715…21acf8

In the attack transaction, the attacker constructed a message that contained valid signatures and passed a crafted ns parameter (which contains a large number of zUSD). As a result, the attacker used 300 REI to swap 700k zUSD.

Three addresses that are collated with the signatures are:

0x0d93A21b…76261C

0x3054e197…67aa4a

0x4448993f…77dfd2

Incident Report

Protocol / Project Zerogoki
Date of Incident
Attack Technique Other
Classification Other
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exploit/Other
Affected Token REI
Official Website zerogoki.org/
Protocol Twitter/X @0Zerogoki
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 Deep understanding of other 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 Zerogoki's contract logic - root cause: other
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 Other audit checklist and test coverage

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

  • Verify all logic paths related to Other are guarded by proper access controls and input validation
  • 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

Sources & References

Learn to Prevent the Next Zerogoki

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