LOO Hack

TOTAL LOST $275K
Low Rugpull

Summarize with AI

Affected Chain 2022 Incident surface
Recovered - No recovery reported
All-Time Rank #1179 By amount stolen
Auditors 1 Prior security audit

Incident Overview

LOO project was rugpulled by the deployer-related address. The scammer drained 275,117 $USD from the liquidity pool.

LOO is a BEP20 token trading on PancakeSwap. The token deployer sent 1,050,000,000 $LOO tokens to an EOA address which drained the liquidity for 275,117 $USD in total. The stolen funds were transferred to another EOA address.

Scammer addresses:

https://bscscan.com/address/0xd9c37a0a…a43194

https://bscscan.com/address/0x36ec92f4…324d6a

https://bscscan.com/address/0xf88e124b…6c67b4

Token transfer transaction:

https://bscscan.com/tx/0xe5c67dff…b5aecd

Stolen funds transfer transaction:

https://bscscan.com/tx/0xed08f931…aeac5c

Incident Report

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

Protocol Information

Protocol Type Leveraged Farming
Affected Token LOO
Official Website www.loopfi.xyz/
Protocol Twitter/X @loopfixyz
Team Anonymous
Source Code Verified On-Chain

Market Context at Time of Hack

Token Categories
Memes Solana 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 LOO'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 — still lost $275K. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to LOO, these are the critical security checks that could have prevented this incident (October 2022).

  • 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 LOO

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