Zodiac Credit Hack
Incident Overview
On the 9th of April ZOC on the BSC chain was rugged for approx 77k USD.
The team responsible for managing liquidity in the ZOC protocol executed a liquidity removal scam, causing the project to suffer significant losses. The contract deployer removed a significant amount of liquidity pool (LP) and sold off the token, leading to a sharp drop of around 90% in its initial price.
Scammer:
https://bscscan.com/address/0xfad248b5…f8a28e
Liquidity removal:
https://bscscan.com/tx/0xb7fcda93…63170d
https://bscscan.com/tx/0xec4c14d4…7d381a
https://bscscan.com/tx/0x6e950143…99ac0d
Incident Report
Protocol Information
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.
What Auditors Should Check
If you're auditing a protocol with similar architecture to Zodiac Credit, these are the critical security checks that could have prevented this incident (April 2023).
- Verify all logic paths related to Rugpull 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 TrialSources & References
Learn to Prevent the Next Zodiac Credit
The Zodiac Credit 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.