Fluidkey restored its privacy wallet on November 20, one day after taking the service offline in response to unauthorized transfers. The company released version 1.79.22 for web, iOS and Android, and said older builds will stay disabled. Users must open Settings and select Update before they can send funds again.
The cause, according to the company, was a flaw in a third-party logging tool rather than a compromise of user keys. Fluidkey said private keys never left holders’ devices. It shut services down on November 19 and reported no further unauthorized transactions after the shutdown, while working with the security group SEAL 911 to trace funds.
The sequence left a gap. Fluidkey’s first warning, telling users to avoid the site and app, went out before a fixed version existed, so the service stayed unavailable for roughly a day while the team investigated and rebuilt. Users who needed to move funds during that window had no supported route through the app.
Blockchain analytics firm Bitquery linked at least $1.58 million in payouts to wallets connected to the incident across six chains, including Base and Ethereum, in transfers between 17:28 and 18:04 UTC on November 19. A broader six-chain scan covering 17:10 to 18:10 UTC put the total near $1.6 million. An independent drain tracker maintained by pepebndc estimated about $1.63 million across seven chains in a November 20 morning snapshot.
The raw totals overstate the theft. Bitquery counted roughly $349,000 sent to wallets with an established history, a group that includes ordinary payments made before the drain began. About $277,000 of that arrived during the incident in a pattern the firm read as a single user moving their own funds across Ethereum and Base. A further $65,000 went to destinations Bitquery could not classify, and the tracker excluded one Polygon payout it treated as an owner withdrawal.
Those categories exist because the attribution is inferential. Bitquery reconstructed ownership from wallet activity rather than from user reports, which is why its published figure comes with buckets instead of a single confirmed loss number. The gap between its $1.6 million and the tracker’s $1.63 million reflects that uncertainty, not a disagreement about the incident itself.
The incident is a reminder that self-custody removes one category of risk without eliminating the rest. Keys can stay on a device while the software around them, including logging and other support services, still processes the data needed to move assets. Fluidkey’s users were not asked to rotate keys, and the company’s guidance was to check their own address or transaction hash on-chain if a transfer looked unfamiliar.