On February 2024, SMOOFSStaking suffered a reentrancy — the first of 51 documented reentrancy incidents in our archive where the loss figure was not publicly disclosed but the exploit pattern is documented below.
Attack Mechanics: How the SMOOFSStaking Reentrancy Played Out
Exploit Class Applied to SMOOFSStaking
The SMOOFSStaking incident on February 28, 2024 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, SMOOFSStaking is 1 of 51 documented reentrancy incidents.
SMOOFSStaking in Context
The SMOOFSStaking incident joins a class whose largest loss to date is Curve (2023) at $41M.
Prior Reentrancy Before SMOOFSStaking
The nearest reentrancy incident before SMOOFSStaking was EGGX, 8 days earlier on February 20, 2024. The same exploit class surfaced again within the reentrancy attack surface.
Impact & Recovery for SMOOFSStaking
SMOOFSStaking Loss Figure
The loss figure for SMOOFSStaking is not publicly disclosed. The primary source reports the exploit in non-USD terms, so no USD estimate is published here. For reference, the average loss across 51 reentrancy incidents in our archive is $2.87M.
Timeline Since the SMOOFSStaking Incident
The SMOOFSStaking exploit occurred 2.1 years ago (776 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for SMOOFSStaking
Public post-mortem / on-chain analysis for the SMOOFSStaking incident: view source.
FAQ
How much did SMOOFSStaking lose?
The SMOOFSStaking loss figure is not publicly disclosed. The primary source reports the exploit in non-USD token terms, so no USD estimate is published here.
When did the SMOOFSStaking hack happen?
The SMOOFSStaking exploit was recorded on February 28, 2024 — 776 days ago.
What type of exploit hit SMOOFSStaking?
The SMOOFSStaking 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 SMOOFSStaking?
Our archive contains 51 documented reentrancy incidents. The SMOOFSStaking incident is one of them.
How does SMOOFSStaking compare to the largest Reentrancy attack?
The largest reentrancy incident in our archive is Curve (2023) at $41M. The SMOOFSStaking loss was not publicly disclosed.
How does the proposed protocol improve upon existing cross-chain solutions?
By achieving secret transmission channels between multiple parties and supporting offline tolerance.
What percentage of companies surveyed have customers asking for more transparency in transactions?
61% of companies reported their customers demand more transparency.