How much was lost in the Eth Contingency hack?

The Eth Contingency hack resulted in $25.0M in losses on November 08, 2017.

What attack technique was used in the Eth Contingency exploit?

The Eth Contingency exploit utilized Rugpull. Understanding this attack vector is critical for smart contract auditors and developers building secure DeFi protocols.

How can developers prevent similar smart contract attacks?

Preventing smart contract hacks requires a combination of secure coding practices, thorough security audits, and understanding common attack vectors like reentrancy, oracle manipulation, and access control flaws. Smart Contract Hacking (SCH) provides hands-on training to help developers and auditors identify and prevent vulnerabilities before deployment.

Eth Contingency Hack

TOTAL LOST $25.0M

High #199 All-Time Nov 08, 2017 Rugpull

Affected Chain 2017 Incident surface

Recovered - No recovery reported

All-Time Rank #199 By amount stolen

Protocol Type Exit Scam/Rugpull Target category

Incident Overview

Quick Summary

EthContingency ICO scam resurfaces with dormant funds worth $13.5 million.

Details of the Exploit

EthContingency conducted an ICO in early 2017, raising a substantial amount of 21,144 ETH when the price of ETH was approximately $17. However, shortly after the ICO, the project team disappeared, leaving investors empty-handed. Despite the team's disappearance, they retained control over the majority of the raised funds.

Surprisingly, between 2021 and 2022, the dormant EthContingency team resurfaced, transferring over $25 million worth of ETH to the privacy-focused mixer, Tornado Cash. The sudden movement of funds raised eyebrows within the crypto community, shedding light on the abandoned ICO project's reemergence after years of silence.

Currently, the EthContingency team still holds over 4600 ETH, equivalent to $13.5 million, across multiple wallet addresses. These funds remain untouched and dormant, raising questions about the team's intentions and the possibility of further actions with the remaining assets.

Block Data Reference

ICO Address: 0xc96eec41…a97401

Wallet Addresses with Dormant Funds:

0x89e28ec9…f44ed3: 2365 ETH

0xbb4ed2b0…b56c0e: 1619 ETH

0x5472d797…618840: 404 ETH

0x139bcb54…1be961: 79 ETH

0x4c756e1c…02b859: 64 ETH

Incident Report

Protocol / Project Eth Contingency

Date of Incident November 08, 2017

Attack Technique Rugpull

Classification Other

Primary Source View Post-Mortem

Protocol Information

Protocol Type Exit Scam/Rugpull

Affected Token CTY

Protocol Twitter/X @EthContingency

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 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 Eth Contingency's contract logic - root cause: other

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 Eth Contingency, these are the critical security checks that could have prevented this incident (November 2017).

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

01
Source 1 https://twitter.com/zachxbt/status/1760999901318754712

Threat Assessment

Severity Level

HIGH

Attack Vector Rugpull
Root Cause Other
Year 2017

Learn to Prevent the Next Eth Contingency

The Eth Contingency 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