Security Hub

Fluidkey's $1.6M Hack Tests the Limits of Local Key Storage

Published: Nov 21, 2026•By Aleksandar Dukic

Key Analysis

Fluidkey restored its wallet after a reported $1.6 million theft. The incident puts app security, relayer activity and the limits of local key storage in focus.

Fluidkey's $1.6M Hack Tests the Limits of Local Key Storage

Listen To This Article

Fluidkey's $1.6M Hack Tests the Limits of Local Key Storage

4m 40s audio

AI narration. Useful for scanning on the move. Names and tickers may be mispronounced.

Fluidkey has restored its web, iOS and Android wallet apps after unauthorized transfers led it to suspend services on November 19. As of November 21, 2026, CryptoSlate reports roughly $1.6 million in incident-linked losses and says users must update to version 1.79.22 before sending funds again.

The company attributed the incident to flaws in a third-party logging tool while saying users' private keys remained on their devices. Its response highlights a specific security concern: the software that handles a locally held key can remain a point of exposure.

A 36-minute drain through the relayer

Bitquery's investigation traced at least $1.58 million to attacker-linked wallets across six chains between 17:28 and 18:04 UTC on November 19. Half had left within five minutes. The payouts passed through Fluidkey's own relayer, which submits transactions and pays network fees for users.

Base accounted for about $837,000 of the attributed losses and Ethereum for $660,000. Most stolen assets were dollar stablecoins, including USDC and USDT.

Some users were withdrawing funds during the same period. Bitquery identified approximately $277,000 moving to an older wallet in a pattern it interpreted as one owner transferring their own assets. It kept those payments separate from the attacker-linked total.

Counting every outgoing payment during the incident would combine theft with legitimate withdrawals, overstating the damage. To distinguish between them, Bitquery classified recipients using their transaction histories and subsequent movements.

The transaction trail establishes the route funds took. Fluidkey's reported logging-tool explanation addresses the cause; a full technical account connecting that flaw to the unauthorized transactions was still pending in the reporting reviewed for this article.

Local keys still depend on application code

Fluidkey's technical documentation describes a spending key that controls funds and a viewing key used to find accounts and transactions. In its documented flow for an existing wallet, a user signs a message to derive those keys inside the client. Fluidkey receives a derived viewing-key node so it can generate addresses and retrieve account information.

Its stealth accounts use single-signer Safe smart accounts. Each account has one authorized signer, a design distinct from splitting transaction authority among multiple signing parties.

This arrangement gives users control over their accounts while allowing Fluidkey to handle address discovery and transaction submission. For readers comparing ways to retain control of their wallet keys, those operational dependencies deserve attention alongside the location of the key itself.

Dedaub had examined that dependency in its May 24, 2024 assessment of the Fluidkey Stealth Account Kit. The auditors wrote that legitimate application code kept the spending key on the client, but a compromised server could deliver malicious JavaScript with access to it.

The assessment covered the cryptographic library, rather than the entire Fluidkey service. Its warning describes a design risk, not a finding about the November attack.

The practical implication concerns the software self-custody relies on: local key generation still requires trustworthy software at the moment the key is derived or used. A user can retain their credentials while depending on an application to handle them safely. Reviewing that application boundary is part of assessing custody risk.

Restored access and independent recovery

Fluidkey's restored release requires version 1.79.22, according to CryptoSlate. Older versions remain offline, and the company directed users to Settings and Update to resume transactions. It also said it would contact affected users individually and publish a post-mortem.

The company reported no further unauthorized transfers after taking services offline and said it was working with SEAL 911 on the investigation.

For account holders, restored access and recovery of stolen money are separate outcomes. Reopening an app lets users interact with remaining funds; it does not reverse completed transfers.

Fluidkey also documents an independent recovery route. Its recovery instructions describe SARA as an interface for checking addresses, testing recovery with a test account, or accessing funds as a last resort. The documentation warns that moving funds outside the normal interface may impair functionality inside the app.

That route addresses dependence on Fluidkey's interface for accessing funds still held in an account. Users checking their position should distinguish their remaining balance from unfamiliar historical transactions before treating restored app access as resolution of an individual loss.

Overview

Fluidkey's reported $1.6 million theft combined unauthorized transfers through its relayer with a company statement that private keys stayed on users' devices. The incident demonstrates that assessing wallet safety requires examining the application handling transaction authority as well as key storage.

Fluidkey has restored its apps. Sending funds requires version 1.79.22.

DisclaimerThis article is provided for informational purposes only and does not constitute financial advice. All fee, limit, and reward data is based on issuer-published documentation as of the date of verification.

Have a question or update?

Discuss this analysis with the community on X.

Discuss on X

Comments

Comments are moderated and may take a moment to appear.