On November 2024, Proxy_b7e1 was exploited in a business logic flaw, resulting in approximately $8.5K in losses. That makes the Proxy_b7e1 exploit the 393rd largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the Proxy_b7e1 Business Logic Flaw Played Out
Exploit Class Applied to Proxy_b7e1
The Proxy_b7e1 incident on November 24, 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, Proxy_b7e1 is 1 of 144 documented business logic flaw incidents.
Proxy_b7e1 in Context
At $8.5K, the Proxy_b7e1 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 Proxy_b7e1
The nearest business logic flaw incident before Proxy_b7e1 was MFT, 7 days earlier on November 17, 2024 ($33.7K lost). The same exploit class surfaced again within the business logic flaw attack surface.
Proxy_b7e1 Vulnerability Signature
The primary source categorises the Proxy_b7e1 exploit specifically as “Logic Flaw”. This narrower label is entity-specific: it reflects how the Proxy_b7e1 contract failed, rather than the broad business logic flaw pattern alone.
Impact & Recovery for Proxy_b7e1
Proxy_b7e1 Loss Figure
The Proxy_b7e1 exploit caused $8,500 in losses — a minor (<$1M) incident and the 117th largest of 188 documented in 2024.
Where Proxy_b7e1 Sits Among Business Logic Flaw Attacks
Ranked by loss size, Proxy_b7e1 is the 87th largest of 144 business logic flaw incidents documented. That puts the Proxy_b7e1 loss below the class average of $6.08M.
Timeline Since the Proxy_b7e1 Incident
The Proxy_b7e1 exploit occurred 1.4 years ago (506 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for Proxy_b7e1
Public post-mortem / on-chain analysis for the Proxy_b7e1 incident: view source.
FAQ
How much did Proxy_b7e1 lose?
The Proxy_b7e1 exploit in November 2024 resulted in $8,500 in losses — the 117th largest of 188 DeFi incidents that year.
When did the Proxy_b7e1 hack happen?
The Proxy_b7e1 exploit was recorded on November 24, 2024 — 506 days ago.
What type of exploit hit Proxy_b7e1?
The Proxy_b7e1 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 Proxy_b7e1?
Our archive contains 144 documented business logic flaw incidents. The Proxy_b7e1 incident is one of them.
How does Proxy_b7e1 compare to the largest Business Logic Flaw attack?
The largest business logic flaw incident in our archive is – EulerFinance (2023) at $200M. The Proxy_b7e1 loss is $8.5K.
How are the firms selected for the study?
Firms listed on the Corporate Sustainability Index (CSI) from 2012 to 2016 in the Brazilian stock market's service sector.
What is the purpose of employing SNARKs in the framework?
For efficient and privacy-preserving proof of data authenticity without revealing actual data.