LCX Hack

TOTAL LOST $7.9M
Medium Private Key Compromised (Unknown Method) / Access Control ethereum

Summarize with AI

Affected Chain ethereum Incident surface
Recovered - No recovery reported
All-Time Rank #345 By amount stolen
Protocol Type Exploit/Access control Target category

Incident Overview

LCX hot wallet was compromised, resulting in a loss of approximately $7.94M in various crypto-assets.

LCX's private key to their hot wallet was compromised, allowing the hacker to steal user assets. The stolen assets included ETH, USDC, EURe, SAND Token, LINK, LCX Token, QNT, ENJ, and MKR, totaling approximately $7.94M. The stolen funds were then deposited into a Tornado Cash mixer.

Other LCX wallets such as Bitcoin, HBAR, ADA, DGB, TIA, or DGMV were not impacted. Approximately 611,000 EURe were frozen with the assistance of Monerium.

LCX hot wallet:

https://etherscan.io/address/0x4631018f…503e6f

The hacker's address:

https://etherscan.io/address/0x16540227…560a05

The transaction of stolen funds into Tornado Cash mixer:

https://bloxy.info/txs/calls_from/0x16540227…560a05?signature_id=994162&smart_contract_address_bin=0x722122df…5b6967

Incident Report

Protocol / Project LCX
Date of Incident
Affected Chain(s) ethereum
Attack Technique Private Key Compromised (Unknown Method) / Access Control
Classification Infrastructure / CeFi
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exploit/Access control
Official Website www.lcx.com/
Protocol Twitter/X @lcx
Team Public / Doxxed
Source Code Unverified

Market Context at Time of Hack

Token Categories
Platform Centralized Exchange (CEX) Token Ethereum Ecosystem Alleged SEC Securities

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 LCX'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? Hard to catch — private key / OpSec failures are outside smart contract audit scope

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

  • Verify all logic paths related to Private Key Compromised (Unknown Method) / 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

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 LCX

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