LooBr Hack

TOTAL LOST $147K
Low Rugpull

Summarize with AI

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

Incident Overview

Quick Summary

LooBr project experienced a rugpull by the deployer, resulting in a loss of 147,439 $USD.

Details of the Exploit

LooBr, a cross-chain social-media NFT-Marketplace, was exploited by its deployer who removed liquidity from the LP pool in two separate transactions over a three-day period. Interestingly, the deployer utilized two different tokens carrying the same name during this operation. After the liquidity removal, the funds were transferred through a couple of EOA addresses before being deposited into the Binance Exchange.

It is worth noting that a Meta Ruffy Deployer address was also involved in this incident. The total financial loss from this rugpull is calculated to be 147,439 $USD worth of 614 BNB.

Block Data Reference

Deployer Address:

https://bscscan.com/address/0x79003a10…1be4b1

Scammers' Addresses:

https://bscscan.com/address/0xfa777ea4…739aca

https://bscscan.com/address/0x49273b37…9e6277

Liquidity Removal Transactions:

https://bscscan.com/tx/0xbc8f34cc…95c04d

https://bscscan.com/tx/0x9d25b4eb…7df079

Incident Report

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

Protocol Information

Protocol Type Exit Scam/Rugpull
Affected Token LooBr
Official Website loobr.com/
Protocol Twitter/X @loobr_com
Team Anonymous
Source Code Verified On-Chain

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

Browse all hacks

These hacks used the same attack technique. Understanding the pattern helps prevent future exploits.

Pepe Trump $38K
Rugpull
NYC Memecoin $3.4M
Rugpull
OracleBNB $80K
Rugpull
Aqua $4.7M
Rugpull
Fake LAYER $465K
Rugpull
Gifto $10.0M
Rugpull

Learn to Prevent the Next LooBr

The LooBr 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
Recreate exploit patterns safely Free Trial