Incident Overview
The $JUICE Staking contract was exploited on March 9th, 2024, resulting in the loss of 1,303,811 $JUICE Tokens, which were immediately sold for approximately 54 ETH on Uniswap. The exploit was promptly addressed, and investigations were launched to understand the attack.
The $JUICE Staking contract was exploited on March 9th, 2024, allowing the attacker to drain 1,303,811 $JUICE Tokens and sell them for approximately 54 ETH on Uniswap. The exploit stemmed from vulnerabilities in the staking contract, which enabled the attacker to drain both the liquidity pool and users' staked tokens. Upon discovery, immediate actions were taken to disable the staking site, secure the infrastructure, and initiate investigations.
Contract Drain Transactions:
Transaction 1: https://etherscan.io/tx/0xc9b2cbc1…0991e7
Transaction 2: https://etherscan.io/tx/0x5812894b…731233
Transaction 3: https://etherscan.io/tx/0xf9312da2…5f363d
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 JUICE, these are the critical security checks that could have prevented this incident (March 2024).
- 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 TrialSources & References
Learn to Prevent the Next JUICE
The JUICE 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.