On February 2023, – dForce was exploited in a reentrancy, resulting in approximately $3.65M in losses. That makes the – dForce exploit the 52nd largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the – dForce Reentrancy Played Out
Exploit Class Applied to – dForce
The – dForce incident on February 10, 2023 is classified as a Reentrancy. A malicious contract re-enters a vulnerable function before state is updated, letting it drain funds multiple times. In the full archive, – dForce is 1 of 51 documented reentrancy incidents.
– dForce in Context
At $3.65M, the – dForce exploit is a significant ($1M–$10M) event compared to the largest same-class incident in our archive — Curve (2023) at $41M.
Prior Reentrancy Before – dForce
The nearest reentrancy incident before – dForce was – Orion Protocol, 7 days earlier on February 3, 2023 ($3M lost). The same exploit class surfaced again within the reentrancy attack surface.
– dForce Vulnerability Signature
The primary source categorises the – dForce exploit specifically as “Read-Only-Reentrancy”. This narrower label is entity-specific: it reflects how the – dForce contract failed, rather than the broad reentrancy pattern alone.
Impact & Recovery for – dForce
– dForce Loss Figure
The – dForce exploit caused $3,650,000 in losses — a significant ($1M–$10M) incident and the 15th largest of 214 documented in 2023. This single incident represents 0.6% of all tracked losses that year.
Where – dForce Sits Among Reentrancy Attacks
Ranked by loss size, – dForce is the 4th largest of 51 reentrancy incidents documented. That puts the – dForce loss above the class average of $2.87M.
Timeline Since the – dForce Incident
The – dForce exploit occurred 3.2 years ago (1,159 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for – dForce
Public post-mortem / on-chain analysis for the – dForce incident: view source.
FAQ
How much did – dForce lose?
The – dForce exploit in February 2023 resulted in $3,650,000 in losses — the 15th largest of 214 DeFi incidents that year.
When did the – dForce hack happen?
The – dForce exploit was recorded on February 10, 2023 — 1,159 days ago.
What type of exploit hit – dForce?
The – dForce incident is classified as a Reentrancy. A malicious contract re-enters a vulnerable function before state is updated, letting it drain funds multiple times.
How common is the Reentrancy pattern seen at – dForce?
Our archive contains 51 documented reentrancy incidents. The – dForce incident is one of them.
How does – dForce compare to the largest Reentrancy attack?
The largest reentrancy incident in our archive is Curve (2023) at $41M. The – dForce loss is $3.65M.
What publication trend was observed for articles related to humanitarian supply chains and I4.0?
A gradual increase over time, with a peak in research interest in 2022.
What is the significance of adaptor signatures in the proposed protocol?
They enable the construction of secret transmission channels for cross-chain transactions.