EspressoBot Hack

TOTAL LOST $53K
Low Rugpull

Summarize with AI

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

Incident Overview

EspressoBot deployer performed a rugpull, draining liquidity worth 53,110 USD from UniSwap, resulting in a total loss of 33.04 WETH.

EspressoBot is an ERC20 token trading on UniSwap. On August 8, 2023, the deployer-related address executed an exit scam by draining the liquidity pool in 12 transactions. The stolen funds, amounting to 53,110 USD (equivalent to 33.04 WETH), were transferred through several EOA addresses.

Part of the funds currently remains in another EOA address. It was discovered that the deployer was funded on Binance.

Deployer Address:

https://etherscan.io/address/0x5737083f…a8CdcE

Scammer Address:

https://etherscan.io/address/0xee34Cc55…3C0f18

Funds Holder Address as of Sep 10, 2023:

https://etherscan.io/address/0x13ce2410…ef5579

Liquidity Drain Transactions:

https://etherscan.io/tx/0xe49905a4…4482f0

https://etherscan.io/tx/0xb20a97e2…c83659

Incident Report

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

Protocol Information

Protocol Type Exit Scam/Rugpull
Affected Token ESPS
Official Website espresso.foundation/
Protocol Twitter/X @EspressoBot_ETH
Team Anonymous
Source Code Verified On-Chain

Market Context at Time of Hack

Token Categories
Interoperability Scaling Ethereum Ecosystem Arbitrum Ecosystem Binance Wallet IDO 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 EspressoBot'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 EspressoBot, these are the critical security checks that could have prevented this incident (August 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

Learn to Prevent the Next EspressoBot

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