On April 2024, Hackathon was exploited in a business logic flaw, resulting in approximately $20K in losses. That makes the Hackathon exploit the 331st largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the Hackathon Business Logic Flaw Played Out
Exploit Class Applied to Hackathon
The Hackathon incident on April 14, 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, Hackathon is 1 of 144 documented business logic flaw incidents.
Hackathon in Context
At $20K, the Hackathon 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 Hackathon
The nearest business logic flaw incident before Hackathon was UPS, 5 days earlier on April 9, 2024 ($28K lost). The same exploit class surfaced again within the business logic flaw attack surface.
Impact & Recovery for Hackathon
Hackathon Loss Figure
The Hackathon exploit caused $20,000 in losses — a minor (<$1M) incident and the 93rd largest of 188 documented in 2024.
Where Hackathon Sits Among Business Logic Flaw Attacks
Ranked by loss size, Hackathon is the 68th largest of 144 business logic flaw incidents documented. That puts the Hackathon loss below the class average of $6.08M.
Timeline Since the Hackathon Incident
The Hackathon exploit occurred 2 years ago (730 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for Hackathon
Public post-mortem / on-chain analysis for the Hackathon incident: view source.
FAQ
How much did Hackathon lose?
The Hackathon exploit in April 2024 resulted in $20,000 in losses — the 93rd largest of 188 DeFi incidents that year.
When did the Hackathon hack happen?
The Hackathon exploit was recorded on April 14, 2024 — 730 days ago.
What type of exploit hit Hackathon?
The Hackathon 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 Hackathon?
Our archive contains 144 documented business logic flaw incidents. The Hackathon incident is one of them.
How does Hackathon compare to the largest Business Logic Flaw attack?
The largest business logic flaw incident in our archive is – EulerFinance (2023) at $200M. The Hackathon loss is $20K.
What is the significance of threshold adaptor signatures in the context of blockchain security?
Threshold adaptor signatures enhance security by requiring a subset of key holders to participate, mitigating the risk of a single point of failure.
Explain the main security concerns in traditional data sharing models of the IIoT addressed by the BBDSPP scheme.
The BBDSPP scheme addresses complexities, inflexibility, and security concerns in traditional IIoT data sharing models.