Fluidkey relayer (November 2026) hack — November 2026
Incident facts
| Date of incident | |
|---|---|
| Publicly disclosed | November 19, 2026 |
| Target type | Wallet software or provider |
| Loss | $1,580,000Published estimates range $1,118,222 to $1,634,503Price at time of incident |
| Method | Other or undisclosedProvisional: for 36 minutes Fluidkey's own relayer, the service that submits transactions on users' behalf, paid funds out of user accounts to attacker wallets. Fluidkey has not said how the relayer came to sign them |
| Chains | Base, Ethereum, BNB Chain, Optimism, Arbitrum, Polygon |
| Outcome | Unresolved |
What happened
On 19 November 2026 users of Fluidkey, a privacy wallet that gives each user a name and receives every payment at a fresh address, lost funds on six chains. Between 17:28 and 18:04 UTC Fluidkey's own relayer, the service that pays network fees and submits transactions on users' behalf, sent money out of user accounts. Bitquery counted at least $1.58 million reaching wallets tied to one attacker, half of it within the first five minutes, and found the attacker had put 881.6 ETH, about $1.57 million, into Tornado Cash from six wallets by 21:29 UTC.
An independent tracker published on GitHub, not affiliated with Fluidkey, counts $1,118,222 delivered to confirmed attacker addresses (the low figure here) and $1,634,503 including addresses that only match the pattern (the high figure), most of it on Base and Ethereum. Both counts exclude the roughly $0.3 to $0.4 million that users moved to wallets they already owned while the drain was running.
Fluidkey warned users to stay off its website and app at 18:20 UTC and said that evening that it had taken all services offline at 18:05 UTC, that no unauthorised transaction had gone through since, and that it was working with SEAL 911 on the investigation and on tracing the funds. It has not given a figure or explained how the relayer was made to sign the transfers; a full post-mortem is promised.
Sources
- Fluidkey on X (19 November 2026, 18:20 UTC)Primary · retrieved 2026-11-20
- Fluidkey on X: incident update (19 November 2026, 20:17 UTC)Primary · retrieved 2026-11-20
- Bitquery investigation (20 November 2026)Secondary · retrieved 2026-11-20
- Independent Fluidkey drain tracker on GitHub (checked 20 November 2026, 08:23 UTC)On-chain · retrieved 2026-11-20
- SlowMist Hacked database, Fluidkey entry (19 November 2026)Aggregator · retrieved 2026-11-20
Changes to this entry
- Added at Bitquery's 'at least $1.58m' (low $1,118,222 confirmed and high $1,634,503 confirmed plus suspected, from the independent GitHub tracker at 08:23 UTC 20 Nov). Provisional: Fluidkey has given no figure or cause yet.
Cite this
This data is published under CC BY 4.0. You may reuse it, including commercially, as long as you credit iTokenly and link back.
iTokenly Hack Registry, "Fluidkey relayer (November 2026) hack — November 2026", iTokenly, accessed 2026-11-21, https://itokenly.com/hacks/fluidkey-relayer-november-2026https://itokenly.com/hacks/fluidkey-relayer-november-2026Permalinks never change. If an entry is renamed, the old address keeps working.
Spotted an error? Write to [email protected]. Corrections to published figures are logged on this page. See the methodology for how entries are checked.