Lykke Hack

TOTAL LOST $22.0M
High Other

Summarize with AI

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

Incident Overview

On June 4 Lykke CEX was exploited and lost $22 million worth of crypto assets.

Lykke, a centralized cryptocurrency exchange based in Switzerland, halted withdrawals following a security breach on June 4, which resulted in the loss of over $22 million in crypto assets. The incident was publicly acknowledged by the Lykke team in a social media post on June 10. They assured users that their funds were safe and would be recovered, although both Lykke UK and Lykke Corp AG were affected by the attack.

Incident Report

Protocol / Project Lykke
Date of Incident
Attack Technique Other
Classification CeFi

Protocol Information

Protocol Type Exploit/Other
Official Website www.lykke.com/
Protocol Twitter/X @lykke
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 Lykke's contract logic - root cause: cefi
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 Lykke, these are the critical security checks that could have prevented this incident (June 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 Trial

Sources & References

Learn to Prevent the Next Lykke

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