Bloom Hack

TOTAL LOST $600K
Low Other

Summarize with AI

ChatGPT Perplexity Claude Grok
Affected Chain 2024 Incident surface
Recovered - No recovery reported
All-Time Rank #959 By amount stolen
Auditors 1 Prior security audit

Incident Overview

Quick Summary

On the 9th of May Bloom on Blast was exploited with a losses about 600k USD.

Details of the Exploit

On May 9th, Bloom on Blast was exploited due to an issue with specific Blast L2 rebasing tokens that weren't handled correctly. This vulnerability allowed the exploiter to gain $600,000 by exploiting the vulnerable Trading Blast contract. After that funds were bridged to the Ethereum mainnet.

Block Data Reference

Exploiter:

https://blastscan.io/txs?a=0x60e32939…e181d4&p=2

Contract used for interactions:

https://blastscan.io/address/0xb59b25b2…78f0ab

Vulnerable implementation:

https://blastscan.io/address/0xcc020e81…600afe#code

Funds stored here:

https://etherscan.io/address/0xd6962cac…729834#tokentxns

Incident Report

Protocol / Project Bloom
Date of Incident
Attack Technique Other
Classification Yield Aggregator
Primary Source View Post-Mortem #1 View Post-Mortem #2 View Post-Mortem #3

Protocol Information

Protocol Type RWA
Official Website www.bloom.trading/
Protocol Twitter/X @BloomOnBlast
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
AI & Big Data Gaming Ethereum Ecosystem MVB BNB Chain Ecosystem Binance Alpha Binance Wallet IDO Binance Ecosystem
Protocol Links
Discord

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 other 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 Bloom's contract logic - root cause: yield aggregator
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? Likely — with a thorough Other audit checklist and test coverage
Audited by Audit Report 1 — still lost $600K. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • Verify all logic paths related to Other 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

Browse all hacks

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

DeFiTuna $570K
Other
Cascade $1.3M
Other
Lumi Finance $264K
Other
Hinkal $820K
Other
AIDCToken $121K
Other
Polymarket $3.0M
Other

Learn to Prevent the Next Bloom

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