On June 2024, Crb2 was exploited in a business logic flaw, resulting in approximately $15K in losses. That makes the Crb2 exploit the 356th largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the Crb2 Business Logic Flaw Played Out
Exploit Class Applied to Crb2
The Crb2 incident on June 16, 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, Crb2 is 1 of 144 documented business logic flaw incidents.
Crb2 in Context
At $15K, the Crb2 exploit is a minor (<$1M) event compared to the largest same-class incident in our archive — – EulerFinance (2023) at $200M.
Prior Business Logic Flaw Before Crb2
The nearest business logic flaw incident before Crb2 was JokInTheBox, 5 days earlier on June 11, 2024. The same exploit class surfaced again within the business logic flaw attack surface.
Impact & Recovery for Crb2
Crb2 Loss Figure
The Crb2 exploit caused $15,000 in losses — a minor (<$1M) incident and the 100th largest of 188 documented in 2024.
Where Crb2 Sits Among Business Logic Flaw Attacks
Ranked by loss size, Crb2 is the 75th largest of 144 business logic flaw incidents documented. That puts the Crb2 loss below the class average of $6.08M.
Timeline Since the Crb2 Incident
The Crb2 exploit occurred 1.8 years ago (667 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
FAQ
How much did Crb2 lose?
The Crb2 exploit in June 2024 resulted in $15,000 in losses — the 100th largest of 188 DeFi incidents that year.
When did the Crb2 hack happen?
The Crb2 exploit was recorded on June 16, 2024 — 667 days ago.
What type of exploit hit Crb2?
The Crb2 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 Crb2?
Our archive contains 144 documented business logic flaw incidents. The Crb2 incident is one of them.
How does Crb2 compare to the largest Business Logic Flaw attack?
The largest business logic flaw incident in our archive is – EulerFinance (2023) at $200M. The Crb2 loss is $15K.
What role does the Akaike Information Criterion (AIC) play in the analysis?
AIC helps in model selection by estimating the relative quality of statistical models for a given set of data.
What are the two types of security challenges specifically mentioned as being addressed by blockchain in e-commerce?
The challenges are data breaches/data theft and phishing attacks.