How much was lost in the Dor hack?

The Dor hack resulted in $103K in losses on November 21, 2023.

What attack technique was used in the Dor exploit?

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

Dor Hack

TOTAL LOST $103K

Low Nov 21, 2023 Rugpull

Affected Chain 2023 Incident surface

Recovered - No recovery reported

All-Time Rank #1521 By amount stolen

Protocol Type Exit Scam/Rugpull Target category

Incident Overview

Quick Summary

DOR token was experienced a rugpull by the deployer, resulting in a loss of 102,731 USD from PancakeSwap liquidity pool on Nov 21, 2023.

Details of the Exploit

DOR is a BEP20 token trading on PancakeSwap. The deployer added liquidity to the LP pool and then removed it in a short time frame. The stolen funds, worth 102,731 USD (403.18 WBNB), were transferred to another EOA and subsequently distributed among multiple addresses.

Block Data Reference

Deployer Address:

https://bscscan.com/address/0xB62676f1…938a56

Liquidity Removal Transaction:

https://bscscan.com/tx/0x414a25bb…71ee9b

Incident Report

Protocol / Project Dor

Date of Incident November 21, 2023

Attack Technique Rugpull

Classification Token

Primary Source View Post-Mortem

Protocol Information

Protocol Type Exit Scam/Rugpull

Affected Token DOR

Official Website dyor.com/

Protocol Twitter/X @DYORdotcom

Team Anonymous

Source Code Verified On-Chain

Market Context at Time of Hack

Token Categories

Base Ecosystem

Protocol Links

Discord

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

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/PeckShieldAlert/status/1727147354829324328

Threat Assessment

Severity Level

LOW

Attack Vector Rugpull
Root Cause Token
Year 2023

Learn to Prevent the Next Dor

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