On September 2023, XSDWETHpool 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 XSDWETHpool Reentrancy Played Out
Exploit Class Applied to XSDWETHpool
The XSDWETHpool incident on September 26, 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, XSDWETHpool is 1 of 51 documented reentrancy incidents.
XSDWETHpool in Context
The XSDWETHpool incident joins a class whose largest loss to date is Curve (2023) at $41M.
Prior Reentrancy Before XSDWETHpool
The nearest reentrancy incident before XSDWETHpool was uniclyNFT, 10 days earlier on September 16, 2023. The same exploit class surfaced again within the reentrancy attack surface.
Impact & Recovery for XSDWETHpool
XSDWETHpool Loss Figure
The loss figure for XSDWETHpool 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 XSDWETHpool Incident
The XSDWETHpool exploit occurred 2.6 years ago (931 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for XSDWETHpool
Public post-mortem / on-chain analysis for the XSDWETHpool incident: view source.
FAQ
How much did XSDWETHpool lose?
The XSDWETHpool 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 XSDWETHpool hack happen?
The XSDWETHpool exploit was recorded on September 26, 2023 — 931 days ago.
What type of exploit hit XSDWETHpool?
The XSDWETHpool 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 XSDWETHpool?
Our archive contains 51 documented reentrancy incidents. The XSDWETHpool incident is one of them.
How does XSDWETHpool compare to the largest Reentrancy attack?
The largest reentrancy incident in our archive is Curve (2023) at $41M. The XSDWETHpool loss was not publicly disclosed.
How does the document assess the efficiency and memory of cryptocurrencies?
By using the Hurst exponent to determine if cryptocurrencies have persistent, anti-persistent, or random behaviors.
What are LSTM networks commonly used for in this study?
LSTM networks are used for sequence learning of financial time series data.