How much was lost in the Relay3rV1 hack?

The Relay3rV1 hack resulted in $8K in losses on November 11, 2020.

What attack technique was used in the Relay3rV1 exploit?

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

Relay3rV1 Hack

TOTAL LOST $8K

Low Nov 11, 2020 Rugpull ethereum

Affected Chain ethereum Incident surface

Recovered - No recovery reported

All-Time Rank #1954 By amount stolen

Protocol Type Exit Scam/Rugpull Target category

Incident Overview

The contract deployer added initial liquidity at:

https://etherscan.io/tx/0xe54c922e…1f5146

The liquidity was removed multiple times by the contract deployer:

https://bloxy.info/ru/txs/references_address/0xaa9e20ba…971e4d?argument=to&signature_id=1111734

Incident Report

Protocol / Project Relay3rV1

Date of Incident November 11, 2020

Affected Chain(s) ethereum

Attack Technique Rugpull

Classification Token

Primary Source View Post-Mortem

Protocol Information

Protocol Type Exit Scam/Rugpull

Affected Token RL3R

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 Relay3rV1's contract logic - root cause: token

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 Relay3rV1, these are the critical security checks that could have prevented this incident (November 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://twitter.com/WARONRUGS/status/1325926361987420160
02
Web Archive https://archive.ph/BuSGX

Threat Assessment

Severity Level

LOW

Attack Vector Rugpull
Root Cause Token
Year 2020

Learn to Prevent the Next Relay3rV1

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