Solflare says staking provider security incident halted its validator’s rewards
- Published
- Updated
- Since then
- 6 new reports
- In
- Solana
Solflare said a security incident at a third-party staking provider affected keys for its legacy Solana validator and interrupted staking rewards. The wallet said users’ SOL stayed in their own stake accounts, and it later brought a replacement validator online while preparing a migration path for affected delegations.
Key claims & sources
What it means
Solflare is a non-custodial Solana wallet that, like most retail staking products, does not run its own validator hardware; it delegates user SOL to third-party node operators who handle block production and key custody. That split between wallet interface and validator infrastructure is standard practice across Solana staking services. On Tuesday evening, at 7:26 p.m. ET, Solflare told users its outsourced operator had reported a security incident involving the validator's signing keys, halting reward production.
For the roughly 1.56 million SOL delegated to the affected node, holders keep their principal in their own stake accounts but stop earning rewards until the keys are replaced. Solflare's fix is an in-app migration that will move delegators to a new validator, a manual step users will need to approve rather than something that resolves on its own. Until that migration lands, affected stakers are locked out of yield while facing no direct loss of principal.
The episode tests how much 'non-custodial' promises actually cover. Solflare is right that stake accounts remain owned by users and untouched, since Solana's architecture keeps delegated SOL separate from a validator's operating keys. But reward generation still depends on a single third party's key hygiene, a dependency invisible to most delegators until it breaks. A wallet can be non-custodial for funds and still carry concentrated operational risk for income.
Watch Solflare's in-app migration tool: its rollout date, and whether delegators must manually re-stake or get moved automatically, will determine how quickly reward flow resumes for the 1.56 million SOL affected. Also open is whether the unnamed staking provider discloses what compromised its validator keys, since that answer shapes whether other wallets relying on the same operator face parallel exposure.
Market reaction i
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.
Thefts of a similar size
| When | What happened | Figure |
|---|---|---|
| 6.2 years ago | YFValue · Staking pool vulnerability incident | $170M |
| 8.7 years ago | BitGrail · Improper Access Control incident | $170M |
| 4.1 years ago | Wintermute · Phishing incident | $160M |
| 4.9 years ago | BitMart · Wallet stolen incident | $150M |
| 6.1 years ago | KuCoin · Wallet stolen incident | $150M |
4280 incidents stored · 49 were as large as this one or larger ($160M)