Crypto.com Hack

TOTAL LOST $34.4M
High #158 All-Time Private Key Compromised (Unknown Method) / Access Control bitcoin ethereum

Summarize with AI

ChatGPT Perplexity Claude Grok
Affected Chain bitcoin 2 chains affected
Recovered $34.4M 100.0% returned
All-Time Rank #158 By amount stolen
Protocol Type CEX Target category

Incident Overview

Quick Summary

Crypto.com's user accounts were breached, bypassing the 2FA authentication control, and leading to the theft of ETH, BTC, and other currencies.

Details of the Exploit

On 17 January 2022, unauthorized activity was detected on a few user accounts on Crypto.com. Transactions were being approved without the 2FA authentication control being inputted by the user. This led to an immediate investigation, during which all withdrawals on the platform were suspended. The impacted accounts were fully restored, and all customer 2FA tokens were revoked. Additional security measures were put in place, requiring all customers to re-login and set up their 2FA token. The withdrawal infrastructure was down for approximately 14 hours.

Stolen funds:

- 4,836.26 ETH

- 443.93 BTC

- $66,200 in other currencies

The stolen funds were deposited into a Tornado Cash mixer.

Block Data Reference

The attacker's address:

https://etherscan.io/address/0x6e1218c5…d29d3d

The transaction behind the attack:

https://bloxy.info/txs/calls_from/0x6e1218c5…d29d3d?signature_id=994162&smart_contract_address_bin=0x722122df…5b6967

This is classified as a Access Control Attacks . Compare similar hacks →

Incident Report

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

Protocol Information

Protocol Type CEX
Official Website crypto.com/
Protocol Twitter/X @cryptocom
Team Public / Doxxed
Source Code Unverified

Market Context at Time of Hack

Token Categories
[Deprecated] ICP Ecosystem Internet Computer Ecosystem DePIN
Protocol Links
GitHub

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 Crypto.com'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 Crypto.com, 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

Funds Recovery

100.0%

Recovered

$34.4M

Net Loss

0

Related Attack Classes

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

See all Access Control Attacks examples →

Access Control Attacks

Sources & References

Browse all hacks

These hacks used the same attack technique. Understanding the pattern helps prevent future exploits.

ZKsync $5.0M
Private Key Compromised (Unknown Method) / Access Control
Berally $90K
Private Key Compromised (Unknown Method) / Access Control
Orange Finance $840K
Private Key Compromised (Unknown Method) / Access Control
DeltaPrime $6.0M
Private Key Compromised (Unknown Method) / Access Control
BtcTurk $54.0M
Private Key Compromised (Unknown Method) / Access Control
DMM Bitcoin $305M
Private Key Compromised (Unknown Method) / Access Control

Learn to Prevent the Next Crypto.com

The Crypto.com 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.

Start Free Trial Browse Attack Library
Recreate exploit patterns safely Free Trial