On December 2022, – ElasticSwap was exploited in a business logic flaw, resulting in approximately $845K in losses. That makes the – ElasticSwap exploit the 96th largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the – ElasticSwap Business Logic Flaw Played Out
Exploit Class Applied to – ElasticSwap
The – ElasticSwap incident on December 13, 2022 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, – ElasticSwap is 1 of 144 documented business logic flaw incidents.
– ElasticSwap in Context
At $845K, the – ElasticSwap 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 – ElasticSwap
The nearest business logic flaw incident before – ElasticSwap was – SEAMAN, 14 days earlier on November 29, 2022. The same exploit class surfaced again within the business logic flaw attack surface.
Impact & Recovery for – ElasticSwap
– ElasticSwap Loss Figure
The – ElasticSwap exploit caused $845,000 in losses — a minor (<$1M) incident and the 11th largest of 129 documented in 2022. This single incident represents 0.4% of all tracked losses that year.
Where – ElasticSwap Sits Among Business Logic Flaw Attacks
Ranked by loss size, – ElasticSwap is the 17th largest of 144 business logic flaw incidents documented. That puts the – ElasticSwap loss below the class average of $6.08M.
Timeline Since the – ElasticSwap Incident
The – ElasticSwap exploit occurred 3.3 years ago (1,218 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for – ElasticSwap
Public post-mortem / on-chain analysis for the – ElasticSwap incident: view source.
FAQ
How much did – ElasticSwap lose?
The – ElasticSwap exploit in December 2022 resulted in $845,000 in losses — the 11th largest of 129 DeFi incidents that year.
When did the – ElasticSwap hack happen?
The – ElasticSwap exploit was recorded on December 13, 2022 — 1,218 days ago.
What type of exploit hit – ElasticSwap?
The – ElasticSwap 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 – ElasticSwap?
Our archive contains 144 documented business logic flaw incidents. The – ElasticSwap incident is one of them.
How does – ElasticSwap compare to the largest Business Logic Flaw attack?
The largest business logic flaw incident in our archive is – EulerFinance (2023) at $200M. The – ElasticSwap loss is $845K.
What is the reported accuracy of the proposed financial anti-fraud model?
The model's accuracy reached 93.82%, a notable improvement over baseline algorithms.
What time period does the study cover?
2010–2018.