IPO Hack

TOTAL LOST $585K
Low Rugpull

Summarize with AI

Affected Chain 2023 Incident surface
Recovered - No recovery reported
All-Time Rank #967 By amount stolen
Auditors 2 Prior security audits

Incident Overview

IPO project was rugpulled through custom pools by scammers who drained assets worth 585,153 $USD in two transactions

IPO is a BEP20 token trading on custom liquidity pools on Binance Smart Chain. The deployer created these pools with unverified source code, which allowed certain addresses to use privileged functions and drain the pool. On June 20, 2023, the pool was drained for 102,164 $USDT, part of a total loss amounting to 585,153 $USD.

Deployer Address:

https://bscscan.com/address/0x32e4152e…18d079

Scammer Addresses:

https://bscscan.com/address/0x7861f822…227682

https://bscscan.com/address/0x35fef3c5…7bfc7b

Funds Holder Address:

https://bscscan.com/address/0xc18fbb46…0fef27

Malicious Contract:

https://bscscan.com/address/0x4b50a547…67a20c

Draining Transactions:

https://bscscan.com/tx/0x6f678313…c65264

https://bscscan.com/tx/0xadfb6755…7fd161

Incident Report

Protocol / Project IPO
Date of Incident
Attack Technique Rugpull
Classification Token

Protocol Information

Protocol Type Liquid Staking
Affected Token IPO
Official Website hipo.finance
Protocol Twitter/X @hipofinance
Team Anonymous
Source Code Unverified

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 IPO'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
Audited by Audit Report 1, Audit Report 2 — still lost $585K. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to IPO, 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

Security Audit History

Sources & References

Learn to Prevent the Next IPO

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