Exco Hack

TOTAL LOST $460K
Low Rugpull

Summarize with AI

Affected Chain 2015 Incident surface
Recovered - No recovery reported
All-Time Rank #1035 By amount stolen
Protocol Type Exit Scam/Rugpull Target category

Incident Overview

Exco.in suffered an attack that may have resulted in the loss of up to 2,000 BTC, according to some reports.

Exco.in believes one of their competitors may know the identity of the hacker who attacked them. The alleged hacker goes by the name "ambiorx," and Exco.in says the Danish-based exchange CCEDK knows who he is.

CCEDK's founder appears to have posted conversations he had with a user who had found an exploit in Exco.in. Additionally, Exco.in has revealed that they believe DD4BC, the notorious hacking group responsible for attacks on both Bitalo and Nitrogensports.eu, was involved in the attack. DD4BC performed a DDoS attack on Exco.in. During that time, ambiorx allegedly hacked into Exco.in and pulled off the theft, according to sources. Other exchanges have also been experiencing downtime, but it is unclear whether the attacks are related.

Incident Report

Protocol / Project Exco
Date of Incident
Attack Technique Rugpull
Classification CeFi
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exit Scam/Rugpull
Official Website exco.in/
Protocol Twitter/X @Nexo
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Services Payments Ethereum Ecosystem Polygon Ecosystem Cardano Ecosystem Alleged SEC Securities Binance Ecosystem Binance Listing

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

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

  • Verify all logic paths related to Rugpull 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 Exco

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