Incident Overview
The USDC pool on Pike Beta was exploited by a hacker on April 26, 2024, resulting in the theft of 299,127 USDC. The exploit was facilitated by forged CCTP messages, allowing the attacker to drain USDC across Ethereum, Arbitrum, and Optimism chains. Protocol functions have been temporarily halted in response to the exploit.
The exploit targeted the USDC pool specifically on Pike Beta, with the hacker utilizing forged CCTP messages to drain USDC from multiple chains, including Arbitrum, and Optimism. However, assets on the Base chain and other chains remain unaffected by the exploit. After the exploit stolen funds were bridged the Ethereum mainnet and deposited to the tornado cash.
Exploiter:
Exploiter tx example:
https://optimistic.etherscan.io/tx/0x12770a72…a890e2
https://arbiscan.io/tx/0x979ad9b7…87667f
Tornado deposits:
https://etherscan.io/address/0xadaf1626…04c1d0
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 Pike Finance, these are the critical security checks that could have prevented this incident (April 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 Pike Finance
The Pike Finance 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.