Researchers Flag Swell Rate Manipulation After Railway Key-Drain Warning

0Importance
closedStatus
4News media
Published
Updated

Swell paused deposits and withdrawals for swETH and rswETH after exchange rates for both tokens were flagged as inflated. The latest coverage adds that the protocol said it needed to restore NAV before reopening, and one report said the onchain controls now block withdrawal requests and ETH claims.

Key claims & sources

✓
Researchers flagged inflated swETH and rswETH rates after the cloud-platform disclosure, and the reported 2,513 ETH held by Swell was not confirmed as a loss.
✓
Onchain controls now block withdrawal requests and ETH claims for swETH and rswETH through the protocol.
✓
On October 22, Railway said an intruder might have accessed stored customer secrets, and the Swell rate issue surfaced hours later.
✓
Spreek said someone with Swell DAO’s operational hot keys pushed up swETH and rswETH exchange rates to the 1% hourly cap without new ETH behind them.
✓
Swell paused deposits and withdrawals for swETH and rswETH at 2:39 a.m. ET Friday and said it needs to return the tokens’ net asset value to the correct value before reopening them.

What it means

Swell's swETH and rswETH are liquid staking tokens whose exchange rate is meant to climb only as real ETH staking rewards accrue, with a 1% hourly ceiling built in to stop sudden jumps. That ceiling exists because past DeFi exploits have used manipulated price feeds to drain lending pools. Railway is a cloud platform used by developers to store and deploy secrets such as API keys, making it an unlikely but plausible entry point into a protocol's operational controls.

Holders of swETH and rswETH, and any protocol that accepts them as collateral, now have to treat the posted exchange rate with suspicion until Swell confirms what backs it. Lending markets and DEX pools referencing these tokens face a choice between pausing integrations or risking mispriced liquidations. Swell DAO must rotate the compromised operational hot keys and show auditors that the 2,513 ETH in question is still on-chain before trust in the rate feed can be restored.

A protocol advertising decentralised governance but running its rate updates through hot keys controlled by a small operational team is not fully decentralised in the way users assume. The episode sits inside a wider pattern where the weak point in DeFi is rarely the smart contract itself but the infrastructure and credentials around it, from cloud dashboards to multisig signers. That gap between code security and operational security is where real losses keep originating.

Whether the 2,513 ETH tied to Swell turns out to be a confirmed loss or an accounting artefact of the rate spike is the open question, and Swell's own disclosure will settle it. Railway's investigation into the scope of the October 22 secrets exposure is the second thing to watch, since it will show whether other protocols using the platform face the same hot-key risk.

Market reaction i

EthereumETH the event is about this asset

Ethereum fell 1.5% in the 4 hours after the first headline, after rising 0.3% in the 2 hours before.

$2,410 price at the headline
+0.3% 2 h before
-1.5% 4 h after
-0.9% 12 h after
First headline

48 prices, one every 30 minutes

Coverage timeline

Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.

first
Oct 22 14:18
+12 min
Oct 22 14:31
Crypto Briefing context
Its angle: vulnerabilities, compromises, emphasizing
+16 h 31 m
Oct 23 06:50
The Defiant context
Its angle: withdrawal, requests, controls; with quotes
+18 h 54 m
Oct 23 09:12
CR Cryptopolitan context
Its angle: compromised, operational, submission; with quotes
+1 d 10 h
Oct 24 01:05

Other recent incidents

WhenWhat happenedFigure
2 days ago B18 TimeBank · Unknown incident $404.5k
3 days ago MORE Markets · Unknown incident $308k
3 days ago Lighter incident $10.4M
3 days ago Optimizely (OPTIMJACK) · Supply Chain Attack incident $2.3k
4 days ago Luxor Commander · Unknown incident no figure in dollars

4332 incidents stored