On February 2024, BlueberryProtocol was exploited in a business logic flaw, resulting in approximately $1.4M in losses. That makes the BlueberryProtocol exploit the 80th largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the BlueberryProtocol Business Logic Flaw Played Out
Exploit Class Applied to BlueberryProtocol
The BlueberryProtocol incident on February 23, 2024 is classified as a Business Logic Flaw. A business-logic bug in the contract — such as an incorrect formula or missing state update — lets the attacker withdraw more than their share. In the full archive, BlueberryProtocol is 1 of 144 documented business logic flaw incidents.
BlueberryProtocol in Context
At $1.4M, the BlueberryProtocol exploit is a significant ($1M–$10M) event compared to the largest same-class incident in our archive — – EulerFinance (2023) at $200M.
Prior Business Logic Flaw Before BlueberryProtocol
The nearest business logic flaw incident before BlueberryProtocol was XSIJ, 24 days earlier on January 30, 2024 ($51K lost). The same exploit class surfaced again within the business logic flaw attack surface.
BlueberryProtocol Vulnerability Signature
The primary source categorises the BlueberryProtocol exploit specifically as “logic flaw”. This narrower label is entity-specific: it reflects how the BlueberryProtocol contract failed, rather than the broad business logic flaw pattern alone.
Impact & Recovery for BlueberryProtocol
BlueberryProtocol Loss Figure
The BlueberryProtocol exploit caused $1,400,000 in losses — a significant ($1M–$10M) incident and the 18th largest of 188 documented in 2024. This single incident represents 0.4% of all tracked losses that year.
Where BlueberryProtocol Sits Among Business Logic Flaw Attacks
Ranked by loss size, BlueberryProtocol is the 14th largest of 144 business logic flaw incidents documented. That puts the BlueberryProtocol loss below the class average of $6.08M.
Timeline Since the BlueberryProtocol Incident
The BlueberryProtocol exploit occurred 2.1 years ago (781 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for BlueberryProtocol
Public post-mortem / on-chain analysis for the BlueberryProtocol incident: view source.
FAQ
How much did BlueberryProtocol lose?
The BlueberryProtocol exploit in February 2024 resulted in $1,400,000 in losses — the 18th largest of 188 DeFi incidents that year.
When did the BlueberryProtocol hack happen?
The BlueberryProtocol exploit was recorded on February 23, 2024 — 781 days ago.
What type of exploit hit BlueberryProtocol?
The BlueberryProtocol incident is classified as a Business Logic Flaw. A business-logic bug in the contract — such as an incorrect formula or missing state update — lets the attacker withdraw more than their share.
How common is the Business Logic Flaw pattern seen at BlueberryProtocol?
Our archive contains 144 documented business logic flaw incidents. The BlueberryProtocol incident is one of them.
How does BlueberryProtocol compare to the largest Business Logic Flaw attack?
The largest business logic flaw incident in our archive is – EulerFinance (2023) at $200M. The BlueberryProtocol loss is $1.4M.
What is the primary finding regarding the distribution of cryptocurrency returns?
The returns are non-normal, and no single distribution fits well to all analyzed cryptocurrencies.
In what way does the paper contribute to the field of blockchain and cryptocurrency?
The paper formalizes the security models for multi and threshold adaptor signatures, providing security proofs and demonstrating their applications in blockchains.