How much was lost in the CREW hack?

The CREW hack resulted in $6K in losses on December 12, 2020.

What attack technique was used in the CREW exploit?

The CREW 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.

CREW Hack

TOTAL LOST $6K

Low Dec 12, 2020 Rugpull ethereum

Affected Chain ethereum Incident surface

Recovered - No recovery reported

All-Time Rank #1974 By amount stolen

Protocol Type Exit Scam/Rugpull Target category

Incident Overview

The project was holding a fundraising event:

https://archive.is/8bDTt

The presale contract:

https://etherscan.io/address/0xD5862D56…e4F586

Raised funds (10.8 ETH) were distributed to the external address at:

https://bloxy.info/txs/transfers_from/0xd5862d56…e4f586?currency_id=1

Incident Report

Protocol / Project CREW

Date of Incident December 12, 2020

Affected Chain(s) ethereum

Attack Technique Rugpull

Classification Other

Primary Source View Post-Mortem

Protocol Information

Protocol Type Exit Scam/Rugpull

Affected Token CREW

Official Website crewmates.org/

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 ethereum smart contracts and deploy a custom exploit contract

Protocol Analysis Identification of the exploitable vulnerability in CREW'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 CREW, these are the critical security checks that could have prevented this incident (December 2020).

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://t.me/defiyield_ann/269
02
Web Archive https://web.archive.org/web/20201207203905/https://crewmates.org/

Threat Assessment

Severity Level

LOW

Attack Vector Rugpull
Root Cause Other
Year 2020

Learn to Prevent the Next CREW

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