Mentioned in This Article
1. Swell swETH withdrawals halted: what happened
Swell, a liquid staking protocol built around ether, suspended deposits and withdrawals for its swETH and rswETH tokens at 2:39 a.m. ET on Friday, October 23, 2026. The team said the pause will remain until it restores each token's net asset value, or NAV, to what it called the correct level. As a result, holders cannot redeem either token through the protocol for now, and Swell has not said when access will return.
The freeze follows two days of warnings from on-chain researchers that the exchange rates published by the two token contracts were climbing without any matching increase in the ether behind them. Swell has said all funds are safe, but it has not named a cause and has offered no timeline for a reopening.
For anyone holding the tokens, the practical effect is that the only way out is the open market, where the price is well below what the contracts claim each token is worth.
2. What are swETH and rswETH?
Both tokens are receipts for staked ether (ETH). A user who deposits ETH with a liquid staking protocol receives a token that represents the deposit plus the staking rewards it earns over time. Because rewards accumulate, a single token is worth slightly more ETH as time passes, and the protocol tracks that relationship through an exchange rate stored in the token's smart contract.
That rate matters well beyond the protocol itself. Lending markets, decentralized exchanges and other applications often read it directly to value the token. If the number is accurate, the token can be redeemed for the ETH it states. If the number is inflated, anyone who relies on it is working with a figure the underlying assets do not support.
In normal conditions the rate rises slowly and steadily, in line with staking returns. Sharp or unexplained jumps are therefore treated as a warning sign, which is the pattern researchers say they saw here.
Liquid staking exists to solve a basic trade-off. Staked ether is normally tied up in the network and cannot be spent or lent, so protocols issue a tradable token in its place. That token can then be used elsewhere in decentralized finance, for example as collateral for a loan or as one side of a trading pair. The arrangement works only as long as holders trust that the token can be exchanged for the ETH it represents, which is why a pause on redemptions draws such close attention.
3. How far the contract rates have drifted
At 4:48 p.m. ET on Friday, a reading of the contracts showed swETH at about 1.203 ETH and rswETH at about 1.138 ETH. On-chain analyst Spreek had identified the last clean rates as 1.133 ETH for swETH and 1.082 ETH for rswETH. That puts the current contract figures roughly 6% and 5% above the last readings he considered sound.
Market prices tell a different story. On decentralized exchanges, swETH traded at about 1.089 WETH in a Uniswap pool that held roughly $143,000 in liquidity, while rswETH changed hands at about 1.029 WETH on Curve. Both prices sit well beneath the figures the contracts report, meaning traders are valuing the tokens far below the rates the code advertises.
The size of the gap is notable because the DEX prices are close to, and in some cases below, the last clean contract rates. In other words, the market appears to have priced the tokens as though the inflated increase never happened. The thin liquidity in the Uniswap pool also means that even a modest trade could move that quoted price, so it should be read as an indication of sentiment rather than a deep market.
4. How the rates started to rise
The first public alert came at 9:28 p.m. ET on Wednesday, October 21, when Spreek posted that the admin keys controlling both tokens appeared to be compromised. He said the NAV was being raised by as much as 1% per hour with nothing backing the increase. He also reported that four malicious upgrade contracts had been deployed, capable of moving about 2,500 ETH, although none had been queued through Swell's multisignature wallet, the approval mechanism that normally gates changes of that kind.
Odysseus, the founder of Phylax Systems, described the episode as resembling abuse of a bot key. He stressed that the 2,513 ETH involved is not a confirmed loss, meaning the figure reflects the amount exposed or held rather than a realized theft.
At 11:03 p.m. ET the same night, Swell said it was investigating alongside security partners. It stated that no ETH had left the deposit or withdrawal contracts for swETH or rswETH. That statement is consistent with its later message that funds are safe, though the protocol has not explained how the exchange rates came to be altered.
5. Why is the cause still unconfirmed?
Swell has not confirmed how the incident began, and the researchers who flagged it have been cautious about drawing conclusions. Both raised a possible connection to Railway, a cloud platform that developers use to deploy applications. In a security disclosure dated October 21, Railway said an unauthorized third party may have gained access to customers' encrypted environment variables and read some of them in decrypted form. Environment variables are where teams commonly store credentials such as keys used by automated systems.
Railway's disclosure does not mention Swell, and Swell has neither confirmed nor ruled out any link to the platform. The possibility therefore remains a line of inquiry rather than a finding.
Spreek has also published an incident report, which he said was written with the help of AI and not fully checked. It concluded that as of late October 21, none of the lending protocols Aave, Spark or Fluid accepted either token as collateral. A Morpho market that priced its assets off the contract rate had about 34 ETH available to borrow. Those figures suggest the direct exposure through major lending venues was limited at that point, though they come from an unverified report.
Researchers also noted that the deployment of malicious upgrade contracts that were never queued through the multisig is significant in itself. A multisig requires several designated signers to approve a change, so contracts that exist but have not been put through that process are, at least on the available evidence, prepared rather than executed. That detail is part of why the 2,500 ETH figure is described as reach or exposure and not as funds that have gone missing.
6. How much money is at stake?
According to DefiLlama, swETH holds about $29 million in total value locked, and rswETH holds roughly the same amount. Those totals are small next to the largest liquid staking protocols, but they represent real holders who currently cannot withdraw.
The distinction between value held and value lost is central to the incident. Odysseus's figure of 2,513 ETH describes what was held and potentially exposed, and he was explicit that it is not confirmed loss. Swell's own position is that no ETH has left the relevant contracts. Until the team publishes a full account, the amount, if any, that has been lost remains unestablished.
The inflated exchange rates create a separate risk. If a protocol or a user were to treat swETH as worth 1.203 ETH, they could in theory borrow or redeem against a value that exists only in the contract's reported figure. The pause on deposits and withdrawals is the standard way to stop that from happening while the numbers are repaired.
Pauses of this kind are a common emergency tool in DeFi. Protocols build in the ability to halt deposits and withdrawals so that, if a number or a key is found to be wrong, users cannot take advantage of the error while engineers repair it. The cost is that honest holders are locked out in the meantime, and the length of the lock is usually the main source of anxiety. Here, Swell has tied the reopening to a specific condition, the restoration of correct NAV values, rather than to a calendar date.
7. A reminder from the Kelp DAO exploit
The episode lands in a year when liquid staking and restaking tokens have already been tested by a serious breach. In April, LayerZero linked a $292 million exploit of the bridge used by Kelp DAO's rsETH restaking token to North Korea's Lazarus Group. Kelp DAO later sued LayerZero and its chief executive, Bryan Pellegrino, over the exploit.
The Swell incident is not the same kind of event, and no link between the two has been alleged. The comparison is useful mainly because it shows how a failure in the supporting machinery around a staking token, rather than in Ethereum itself, can leave holders unable to move funds and force protocols to react quickly.
8. What holders should expect next
Swell has said that the next step before it reopens is correcting NAV for both tokens. It has given no date, and it has not issued guidance on whether holders should trade the tokens or keep providing liquidity in pools that include them. Because the tokens now trade well below their contract rates, anyone who sells on a DEX is accepting that discount, while anyone who waits is relying on the protocol to restore redemptions.
The team has also warned that incidents like this tend to attract phishing attempts. Users are likely to see messages claiming to offer recovery or compensation, and the usual precaution applies: rely on the protocol's official channels for announcements and avoid approving any transaction or sharing any key in response to an unsolicited message.
Several questions remain open. Swell has yet to say how the exchange rates were changed, whether the admin keys were in fact compromised, whether the Railway disclosure is relevant, and how it will set the NAV back to a correct value. The answers will determine how quickly the Swell swETH withdrawals can resume and whether holders can exit at the rates the contracts are supposed to represent.