OkayLetsGo Hack

TOTAL LOST $94K
Low Rugpull

Summarize with AI

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

Incident Overview

OkayLetsGo token project was rugpulled by the deployer, who drained the UniSwap pool and removed liquidity. The total loss is 94,230 $USD.

OkayLetsGo is an ERC20 token trading on UniSwap. The OKLG token experienced a significant liquidity removal. Investigation revealed that the token deployer sold a significant amount of tokens in exchange for 50 $ETH to drain the UniSwap pool.

Afterward, two transactions were made from their contract address to remove all remaining liquidity worth 4 $ETH in total. All stolen funds were transferred to another EOA after an incident.

Scammer Address:

https://etherscan.io/address/0xBBb0bB7E…468375

Funds Holder Address:

https://etherscan.io/address/0x47C7c921…Bb1b6F

Draining Transaction:

https://etherscan.io/tx/0x57cee995…e23993

Liquidity Removal Transactions:

https://etherscan.io/tx/0xfb1b1818…90c3b5

https://etherscan.io/tx/0xd1ef2bad…1e08a5

Incident Report

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

Protocol Information

Protocol Type Exit Scam/Rugpull
Affected Token OKLG
Official Website okayeg.vip
Protocol Twitter/X @okayeg_vip
Team Anonymous
Source Code Verified On-Chain

Market Context at Time of Hack

Token Categories
Memes Base Ecosystem

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 OkayLetsGo'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 OkayLetsGo, these are the critical security checks that could have prevented this incident (June 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 OkayLetsGo

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