Fluidkey is a self-custodial privacy wallet. Instead of one public address, each user gets a name, and every payment to that name lands in a fresh stealth address, so outsiders cannot add up what one person holds. On 19 November 2026, money began leaving those addresses without their owners' approval.
Fluidkey posted at 18:20 UTC that it was aware of a security incident affecting users and asked people not to use its website or app. At 20:17 UTC it said there had been no unauthorized transactions since 18:05 UTC, when it took all services offline. It is working with SEAL 911 on the investigation and on tracing funds, the web app and all APIs remain paused until its review is complete, and it will publish a full post-mortem. On the morning of 20 November it warned users about impersonators, saying its team will not contact anyone privately on social media. As of midday on 20 November, Fluidkey has not named a cause, a loss figure or the number of affected users.
What the chain shows
The most detailed public reconstruction so far comes from Bitquery. It found that for 36 minutes, between about 17:28 and 18:04 UTC, Fluidkey's relayer moved funds out of user accounts on Ethereum, Base, BNB Chain, Optimism, Polygon and Arbitrum. Its last transaction came at 18:04:59 UTC, which matches Fluidkey's statement that services went offline at 18:05.
Bitquery counts at least $1.58 million that reached wallets tied to one attacker, with Base and Ethereum carrying most of it. The largest single transaction took about $415,800 in USDT from two accounts on Ethereum. Half of the attacker's take had left within five minutes. Between 20:05 and 21:29 UTC, six wallets deposited 881.6 ETH, about $1.57 million, into Tornado Cash. An independent tracker on GitHub puts the loss at about $1.63 million.
Some of the money that moved during the drain was not stolen. Bitquery counts about $349,000 that went to wallets with an earlier history, most likely the owners' own, including one user who moved about $277,000 to a wallet in use since 2024. That is worth keeping in mind when reading early estimates. Neither Bitquery's figure nor any other has been confirmed by Fluidkey.
Bitquery also found signs of preparation. The attacker's wallets were funded from Tornado Cash in the early afternoon, and small deposits were sent to a few Fluidkey accounts shortly before the main drain, which looks like targets being tested.
What is not known
The chain shows that the relayer sent the payouts. It does not show why. Bitquery lists several explanations that would fit: compromised Fluidkey servers serving malicious code to users, a flaw in the relayer contract, or a stolen key on Fluidkey's side. It notes that a 2024 audit by Dedaub warned that a server compromise could let an attacker push harmful code to users. Until Fluidkey's post-mortem is out, none of these is confirmed.
What privacy wallets add to the attack surface
A privacy wallet protects users from being profiled on a public chain. To do that, it usually adds moving parts that an ordinary wallet does not have.
The first is a relayer. Fresh stealth addresses hold no ETH for gas, so Fluidkey sends transactions on users' behalf. According to Bitquery, a single relayer contract serves all six chains, with one Fluidkey signer per chain. That is convenient, and it also means one component can affect every account at once.
The second is key delegation. Fluidkey's documentation says the spending key stays with the user, while a viewing key goes to Fluidkey so it can generate addresses and detect incoming payments. The service sees more than a plain wallet provider would.
The third is the app itself. Keys are derived in the browser from a signature with the user's existing wallet, so the integrity of the code Fluidkey serves matters as much as the cryptography.
None of this means privacy wallets are unsafe by design. It means "self-custodial" is not the whole story, and the question to ask is which servers, relayers and keys sit between you and your funds, and what happens if one of them misbehaves.
What users should do now
Do not use the Fluidkey website or app until Fluidkey says it is safe. Take updates only from Fluidkey's official X account and its in-app support. Ignore anyone offering to recover funds by direct message. If the wallet you used to derive your Fluidkey keys also secures other funds, review it once the post-mortem explains what was exposed.
We will update this analysis when Fluidkey publishes its post-mortem. A full framework for evaluating privacy tools and their trust assumptions is part of the upcoming Advanced Security Academy.
Sources: Fluidkey posts on X, 18:20 and 20:17 UTC on 19 November and 08:52 UTC on 20 November 2026; Bitquery investigation, figures verified 20 November 2026; CryptoWatchDesk, updated 10:57 UTC, 20 November 2026; PANews, 20 November 2026.