Swell
Why it happened
Attack class: Access controlOperational key custody.
What would have stopped it
- Hold operational keys in separate threshold custody, one blast radius per role.
- Keep proof-of-reserve checks switched on for exchange-rate updates.
What the score saw
Our pre-hack assessment of Swell flagged operational security as its weakest area and noted that its exchange rates come from Swell's own oracle, but it could not see how many hot keys shared one compromise path. It also flagged the upgradeable contracts, the path the attacker went for, and there the multisig and timelock held.
Score dimensions
- Operational securitypartly flagged
- Oracle integritypartly flagged
- Governanceflagged
An attacker gained control of about 30 of Swell's operational hot keys across four chains, including the bot that reports the reserves behind swETH and rswETH, and used it to push both exchange rates up with value that did not exist. The attacker swept only the keys' gas and fee balances, about 6,000 dollars, and Swell says no ETH backing either token moved and no withdrawal was paid at the inflated rate. Four upgrade payloads built to take about 2,513 ETH from Swell's exit and deposit contracts were never installed, because upgrades need a multisig and a seven-day timelock. Swell paused the tokens, reset the rates, and repaid the small shortfall of users who deposited at the inflated rate.
With Swell's compromised oracle bot key, the attacker posted unbacked reprices to the swETH rate oracle and swept the hot keys' gas balances into a hub wallet; the upgrade payloads meant to empty the swETH exit contract were never installed.
Attack flow
All 6 on-chain stepsThe attack in 3 steps. Step 1, Root control: Hot-key balances (source), swETH rate oracle (source). Step 2, Sweep: Attacker hub wallet (attacker), Collection wallet (hub), about $3K reached this step. Step 3, Blocked drain: Lighter deposits (exit).
Step 1: Root control
- SourceHot-key balancesabout 30 keys on four chains~ $6K gas and fees
- SourceswETH rate oraclerates up ~6% and ~5%unbacked, later reset0x289d6004...2d2D71
Step 2: Sweep
- AttackerAttacker hub wallet~ 1.3 ETH swept on Ethereumrewards claimer on 40 staker contracts0x9a475595...ce0f71
- HubCollection wallet37.07 HYPE, 0.079 ETHnever spent0x78fad532...47e773
Step 3: Blocked drain
- ExitLighter depositssmall USDC and ETH tradesthe only cash-out0x3B4D794a...Cf5ca7
Why each step worked
- Oracle bot key0xb29f1af8720e5fd23aa745559d1deaae3d9cda17
- Proof-of-reserve check offmissing controlone key alone set the reserve figure
- Shared hot-key storeone breach exposed every operational role
- Upgrade timelock held4-of-7 multisig plus seven days kept ~2,513 ETH safe
Full forensic detail
Step-by-step reconstruction, root cause, counterfactuals, remediation, and disclosure timeline.
Exploit anatomy
Root cause
The root cause was operational key custody. Swell ran about 30 hot keys for routine jobs across four chains, including the oracle bot that reports the reserves behind swETH and rswETH, strategist keys for its vaults and an EigenLayer operations role. They were exposed together, so one breach handed over every one of those roles at once. The oracle bot alone could set the reserve figure, with the proof-of-reserve check switched off, so the attacker could push exchange rates up with value that did not exist. Two design choices limited the damage: the rate could rise at most 1 percent per hour, and contract upgrades needed a 4-of-7 multisig plus a seven-day timelock, so the four drain payloads the attacker deployed could never be installed. What the attacker actually took was small, the gas and fee balances of the keys, about 6,000 dollars. Per Swell's postmortem, no ETH backing either token moved and no withdrawal was paid at the inflated rate; Swell reset the rates and compensated about 0.25 ETH of depositor shortfall. A possible link to a same-week secrets incident at the Railway cloud platform has been raised but is unconfirmed.
Prevention analysis
With the oracle bot, vault strategists and rewards role held apart, one breach would have exposed one job instead of 30 keys on four chains.
An independent reserve check would have rejected reserve figures that did not match real balances, so the rates could not have been inflated at all.
Per the incident report, lowering a rate triggers a full lockdown, so Swell had to choose between leaving inflated rates in place or halting redemptions. A clean correction path would have shortened the exposure.
Similar incidents
Operational keys that could authorize value were held so that one breach gave the attacker every role it needed. Same root cause: hot-key custody for privileged automated jobs.
Operational hot wallets with protocol-adjacent roles were drained after their keys leaked. Same class: privileged automation keys without threshold custody.
Several operational validator keys were held so that one intrusion reached enough of them to approve withdrawals. Same root cause at far larger scale: many privileged keys sharing one compromise path.
Remediation
Timeline
Get your protocol scored across 12 dimensions, or request ongoing coverage.