Researchers Flag Swell Rate Manipulation After Railway Key-Drain Warning

HACK OR EXPLOITResearchers Flag Swell RateManipulation After RailwayKey-Drain Warning44IMPORTANCEACTIVE3NEWS MEDIA3PIECESOct 22, 2026 14:20blockboard.net

Published Updated 1 new report since it was first published

Researchers said Swell’s swETH and rswETH exchange rates were pushed up after Railway disclosed a possible secrets exposure on October 22. One account said the rates reached the 1% hourly cap without new ETH behind them, while the reported 2,513 ETH tied to Swell was not presented as a confirmed loss.

What this rests on

Claim by claim, with its source
✓
The reported 2,513 ETH held by Swell was not confirmed as a loss.
✓
The episode was described as exposing weaknesses in DeFi protocols and the need for stronger protection against key compromises.
✓
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.

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

ET Ethereum the event is about this asset from 2 h before to 4 h after the line marks the first headline
published
+0.26 % before publication
-1.49 % after
$2,410price at publication
12series points

How the story was built

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
+18 h 54 m
Oct 23 09:12
CR Cryptopolitan context
Its angle: operational, compromised, submitting; with quotes

Other recent incidents

WhenWhat happenedFigure
today Kimchi Token incident $385k
1 days ago WAX Multi-Chain Bridge incident $90.5k
1 days ago NEM(NemTokenV2) incident $821.9k
2 days ago Slice incident $41k
2 days ago Fearless Wallet incident $20k

4221 incidents stored