BlackHart
Go live

Swell

October 21, 2026·Ethereum·Key Compromise
$6K
total loss
StatusConfirmed
View the Swell score →

Why it happened

Attack class: Access control

Operational 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

732Tempered, scored May 15, 2026

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.

ETH backing swETH and rswETHsafe
Exit and deposit contractssafe(about 2,513 ETH protected by the upgrade timelock)
Withdrawalssafe(none paid at the inflated rate)
Hot-key balancesdrained(about 6,000 dollars of gas and fees swept)
Depositors during the incidentpartially affected(about 0.25 ETH shortfall, repaid by Swell)
Exploit anatomy

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.

The 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).

  1. Step 1: Root control

    • Source
      Hot-key balances
      about 30 keys on four chains
      ~ $6K gas and fees
    • Source
      swETH rate oracle
      rates up ~6% and ~5%
      unbacked, later reset
      0x289d6004...2d2D71
  2. Step 2: Sweep

  3. Step 3: Blocked drain

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

1.
Swell's operational hot keys, about 30 across Ethereum, Arbitrum, Base and HyperEVM, came under an outsider's control by 14:25 UTC on October 21, per the incident report by researcher Spreek. Among them was the oracle bot that reports reserves for swETH and rswETH. Swell's postmortem describes a compromised operational key.
2.
Starting at 23:02 UTC the oracle bot key posted unbacked reserve figures, raising the swETH and rswETH exchange rates by the 1 percent per hour maximum. By the time Swell paused, the rates sat about 6 percent and 5 percent above their true values. No withdrawal was paid at the inflated rate.
3.
The attacker swept the gas and fee balances of the hot keys into a hub wallet, 0x9a475595b1e73e5f63b9eaefb46b6d78b8ce0f71, and a collection wallet on HyperEVM: about 1.3 ETH on Ethereum, 37.07 HYPE and about 98 USDC, roughly 6,000 dollars. The hub then traded small amounts on Lighter.
4.
The bot key named the hub wallet as the EigenLayer rewards claimer on 40 rswETH staker contracts, and a compromised strategist key moved 392,891 dollars inside the HLP vault to a sub-account. No rewards had been claimed to the hub as of the report, and Swell reported no loss from the vault.
5.
The attacker deployed four upgrade payloads written to empty Swell's exit and deposit contracts, about 2,513 ETH. They could only be installed through a 4-of-7 multisig and a seven-day timelock, and were never queued.
6.
Swell paused deposits and withdrawals on October 23, reset both rates, reopened on November 1, and on November 2 compensated the depositors who had received too few tokens at the inflated rate, about 0.25 ETH in total.

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

Hold operational keys in separate threshold custody, one blast radius per role.

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.

Keep proof-of-reserve checks switched on for exchange-rate updates.

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.

Let the team mark a rate down without freezing every withdrawal.

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

Fluid (May 2026 reward key compromise)

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.

Polymarket (May 2026 operations wallets)

Operational hot wallets with protocol-adjacent roles were drained after their keys leaked. Same class: privileged automation keys without threshold custody.

Ronin Bridge (2022)

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

1.Swell paused deposits and withdrawals, reset swETH and rswETH to their correct rates, and reopened withdrawals on November 1.
2.Swell compensated the depositors who received too few tokens at the inflated rate, about 0.25 ETH in total, on November 2.
3.Rotate every operational key across all four chains, reset the EigenLayer rewards claimer from a clean key, and remove compromised keys from vault permissions.
4.Move the oracle bot and other privileged automation keys to threshold custody and turn on independent proof-of-reserve checks for rate updates.
5.Integrators that price swETH or rswETH from the contract rate should pin a sanity bound so a sudden unbacked rise cannot be borrowed against.

Timeline

2026-10-21Last normal swETH reprice before the incident.
2026-10-21The compromised oracle bot key funds a fresh deployer wallet; the attacker deploys upgrade payloads soon after.
2026-10-21First unbacked reprice: swETH marked up 1 percent.
2026-10-21Gas and fee balances swept from hot keys into the attacker hub wallet.
2026-10-21Bot key starts naming the hub as EigenLayer rewards claimer on 40 rswETH staker contracts.
2026-10-22swETH marked up for the third time; researcher Spreek publishes an incident report.
2026-10-22Swell says no ETH has left the swETH or rswETH deposit or withdrawal contracts.
2026-10-23Swell pauses deposits and withdrawals for both tokens, working with SEAL 911.
2026-11-01Rates reset and withdrawals reopened; Swell promises compensation within a week.
2026-11-02Swell says compensation to affected depositors is complete.
Spreek (detection and incident report), Odysseas of Phylax Systems (analysis), SEAL 911 (response), Swell (postmortem and compensation), BlackHart (on-chain verification)
Continuous adversarial monitoring

Get your protocol scored across 12 dimensions, or request ongoing coverage.