Fluidkey said on November 20 that it was “back online with v1.79.22 on web, iOS and Android,” a day after taking all services offline during a security incident. In the same post, the company said an attacker “used flaws in a third-party logging tool to obtain session data, prepare unauthorized transfers on our servers, and have them signed when a user opened the app.” Bitquery, which traced payouts on six chains, put at least $1.58 million in wallets it ties to one attacker between 17:28 and 18:04 UTC on November 19. Fluidkey has not published a loss total or named the logging vendor.
What Fluidkey says happened
Fluidkey, a self-custodial wallet that uses stealth addresses, presented the incident as a session-and-server-side problem, not as a theft of seed phrases. “The private keys controlling user funds never left the device,” the November 20 post said. “Transfers can no longer be prepared this way in v1.79.22, which also includes additional safeguards.”
That distinction protected less than it sounds. A key that never leaves the device still signs whatever the app puts in front of it. On Fluidkey’s account, the attacker prepared the transfers on the company’s servers and the app signed them when users opened it, so no key had to be stolen for the money to move.
The company said it would be “reaching out to affected users individually and publish a full post-mortem.” No post-mortem has appeared yet.
The drain, the halt and the first public warning
By Bitquery’s data, unauthorized payouts began at 17:28 UTC on November 19, on Ethereum and Base within seconds of each other. Fluidkey says it took all services offline at 18:05 UTC, 37 minutes later. Its first public warning came at 18:20 UTC, 15 minutes after the halt and 52 minutes after the drain began.
“We are aware of a security incident affecting Fluidkey users. We recommend not interacting with the Fluidkey website and app while we investigate the incident,” Fluidkey said at 18:20 UTC.
At 20:17 UTC, the company said that “there have been no unauthorized transactions since 18:05 UTC, when we took all services offline.” It said it was “working with SEAL 911 on the investigation and on tracing the funds.” As a precaution, “the web app and all APIs remain paused until our review is complete,” with further updates to come “on this channel and in individual support chats.”
On November 20, Fluidkey warned of impersonation attempts. “Our team will not reach out to you privately through social media,” it said. “In doubt, contact our support directly on our website.”
When the apps returned, Fluidkey said previous versions “will remain offline.” To re-enable transactions, it told users to “go to Settings > Update.” It added: “We have implemented a block for all previous versions of the web and mobile app, so you will only be able to transact after the update to the safe new version.”
What the chain shows
Bitquery’s numbers, which it said were verified on November 20, are the data firm’s own estimate, not a Fluidkey total. It said at least $1.58 million reached wallets it ties to one attacker across six chains — Ethereum, Base, BNB Chain, Optimism, Arbitrum and Polygon — and that its range is $1.58 million to $1.64 million. An outside tracker on GitHub, which Bitquery cites, puts the loss at $1.63 million, a figure Bitquery said falls inside its range.
The payouts, Bitquery said, went through Fluidkey’s own relayer, the service that sends users’ transactions and pays the gas. Half of the amount it ties to the attacker had already been paid out by 17:33 UTC, five minutes into the drain. The largest single transaction drained $415,783 in USDT from two accounts on Ethereum. The relayer’s last transaction, Bitquery said, was at 18:04:59 UTC, just before Fluidkey’s stated 18:05 UTC halt.
Bitquery also said that during the drain, one user moved $277,000 across Ethereum and Base to a wallet in use since 2024. The chain, it wrote, does not show whether that user saw the incident coming. Later that evening, six wallets put 881.6 ETH into Tornado Cash between 20:05 and 21:29 UTC, about $1.57 million at Bitquery’s valuation of $1,778 per ether. Transfer data, Bitquery said, shows the payouts but not why the relayer sent them.
It is the second wallet security incident this week. On Tuesday, Trezor said a breach at its shipping partner Skladon had exposed home addresses from 27,000 orders. That was a data leak, not a drain of funds.
FAQ
Were users’ private keys stolen? Fluidkey said the private keys controlling user funds never left the device. It described the attack as session data obtained through a third-party logging tool, unauthorized transfers prepared on its servers, and those transfers signed when a user opened the app.
Can users transact on older versions of the app? Fluidkey said previous versions will remain offline and that it has blocked all previous versions of the web and mobile app. It told users to go to Settings > Update to re-enable transactions in v1.79.22.
Has Fluidkey published a loss total? No. Bitquery traces at least $1.58 million to wallets it ties to one attacker, with a range of $1.58 million to $1.64 million. Fluidkey has not given its own figure or a victim count. It said it is working with SEAL 911 on tracing the funds and will reach out to affected users individually.
Disclaimer: This article is for informational purposes only and does not constitute financial advice.

















