Lympo Hack

TOTAL LOST $18.5M
High Access Control

Summarize with AI

Affected Chain 2022 Incident surface
Recovered - No recovery reported
All-Time Rank #238 By amount stolen
Auditors 1 Prior security audit

Incident Overview

Lympo's operational hot wallet was compromised, leading to the theft of approximately 165.2 million LMT tokens.

On January 10, 2022, at around 2:32 PM (UTC +2), hackers managed to breach Lympo's operational hot wallet. They stole approximately 165.2 million LMT tokens and distributed them to several external addresses. These tokens were subsequently sold on various DEXs.

The compromised wallets:

https://etherscan.io/address/0x5d32b87a…c09e24

https://etherscan.io/address/0x526232f7…29074e

https://etherscan.io/address/0xb0a60eba…dcc342

https://etherscan.io/address/0x934dd627…dc1b2a

https://bscscan.com/address/0x877eecc3…5345a1

https://etherscan.io/address/0x36d97147…c61697

https://etherscan.io/address/0xa432c008…dfbbff

https://etherscan.io/address/0x4b936321…7d484b

https://etherscan.io/address/0x75912da1…665256

Example transaction of the hack:

https://etherscan.io/tx/0x4e476c49…4d1742

Incident Report

Protocol / Project Lympo
Date of Incident
Attack Technique Access Control
Classification NFT

Protocol Information

Protocol Type Gaming
Affected Token LMT
Official Website nft.lympo.io/
Protocol Twitter/X @Lympo_io
Team Public / Doxxed
Source Code Unverified

Market Context at Time of Hack

Token Categories
Base Ecosystem Tokenized Assets Tokenized Real Estate

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 Operational-security tradecraft (phishing, malware, leaked seed phrases, or insider access) to obtain treasury signing authority
Capital Required Minimal capital - only enough to cover gas while draining the compromised accounts
On-Chain Access Valid signing authority over the compromised wallets / multisig signers, allowing direct transfer of funds or stake authorization
Target Reconnaissance Identification of Lympo's high-value treasury accounts and the authority / multisig structure controlling them
Execution Speed Speed to drain the compromised accounts before the team detects the breach and revokes signing authority or freezes the assets
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 Access Control audit checklist and test coverage
Audited by Audit Report 1 — still lost $18.5M. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • Verify all logic paths related to Access Control are guarded by proper access controls and input validation - see the Access Control Attacks attack class for patterns
  • 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

Security Audit History

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Access Control Attacks examples →

Sources & References

Learn to Prevent the Next Lympo

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