HomeCrypto NewsCrypto Hacks & CrimeBitquery Traces at Least $1.58M in a Fluidkey Relayer Drain

Bitquery Traces at Least $1.58M in a Fluidkey Relayer Drain

Bitquery says at least $1.58 million reached wallets tied to one attacker in a 36-minute drain of Fluidkey user accounts on 19 November 2026, after the privacy wallet’s own relayer paid funds out on six chains. In an on-chain investigation whose figures were verified on 20 November, Bitquery’s Gaurav Agarwal puts the payments between 17:28 and 18:04 UTC and says half of the attacker’s take had already been paid out by 17:33. Fluidkey has not published a loss figure of its own.

The company first told users, at 18:20 UTC, that it was aware of a security incident and recommended they stay off its website and app while it investigated. A second post at 20:17 UTC said “there have been no unauthorized transactions since 18:05 UTC, when we took all services offline,” and that it was working with SEAL 911 on the investigation and on tracing the funds, with a full post-mortem to follow. That 18:05 cut-off sits one second after the last relayer transaction Bitquery records, at 18:04:59 UTC.

What Bitquery traced in the Fluidkey drain

Fluidkey is a privacy wallet: each user has a name, and payments land in fresh addresses so that outsiders cannot easily add up a single holding. Bitquery says the company also pays network fees and sends transactions on users’ behalf through a relayer, and that it was this relayer that paid money out of accounts for 36 minutes. The firm reads transfers on Base, Ethereum and four other chains where the relayer paid out.

Not every payment in that hour, Bitquery says, went to the attacker. It traces $349,000 to wallets that already had a history, most likely the owners’ own, including $277,000 moved by one user while the drain was running. The chain, it notes, does not show whether that user saw the drain coming, “nor does it show how the attacker made the relayer pay.” An outside tracker on GitHub puts the loss at $1.63 million, a figure Bitquery says falls inside its own range of $1.58 million to $1.64 million. The number to use is Bitquery’s “at least $1.58 million” to wallets tied to one attacker.

Later that evening, Bitquery says, 881.6 ETH — about $1.57 million — went into Tornado Cash from six wallets between 20:05 and 21:29 UTC. It also records $13,500 in tokenised stocks left on BNB Chain, of which $5,500 reached the attacker. When Bitquery checked at 07:35 UTC on 20 November, nothing further had gone through the relayer.

Fluidkey is back online in v1.79.22

In a third post at 16:10 UTC on 20 November, Fluidkey said it was “back online with v1.79.22 on web, iOS and Android,” and that previous versions would remain offline. To re-enable transactions in the app, it told users to go to Settings > Update, and said it had blocked earlier versions of the web and mobile app. In the same update it offered its own account of the cause: “The 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.” Transfers, it said, can no longer be prepared that way in v1.79.22, which also includes additional safeguards, and “the private keys controlling user funds never left the device.” It said it would reach out to affected users individually and still publish a full post-mortem. That post-mortem has not appeared.

The incident sits in a stretch of wallet-security cases TSN already covers on its Crypto Hacks and Exploits hub, including Keplr’s report that some social-login wallet keys were breached and BTCPay Server’s account of hot wallets being swept on version 2.4.1 and older.

A Bitquery trace is not a company loss figure

Two numbers are circulating as if they were the same fact, and they are not. Bitquery’s “at least $1.58 million” is an on-chain trace of funds that reached wallets it ties to one attacker, bounded by a range that also includes a $1.63 million GitHub tracker figure. Fluidkey has still not said how much was lost. Until it does, or until a post-mortem lands, the Bitquery figure should be kept as Bitquery’s, not rewritten as a company total. The $349,000 that went to wallets with a history during the same hour is also Bitquery’s, and is presented as likely self-transfers rather than as part of the attacker’s take.

The logging-tool explanation should be handled with the same care. It comes from the company’s 20 November update, not from Bitquery, which says the chain does not show how the relayer was made to pay, and not from a completed post-mortem. The company’s statement that private keys never left the device is likewise its own. Both may be right. They are still an interim account of a live investigation, offered as it brought v1.79.22 back online.

What users can act on is narrower and already public. Previous app and web versions remain blocked; transactions, the company says, only resume after the update to v1.79.22. The funds Bitquery followed into Tornado Cash are a tracing result, not a court finding. The next document that would change the picture is the promised post-mortem, or a loss figure from the company itself.

Sources

Related stories

Follow @tsnmediahub on X for breaking AI news as it happens.

Follow on X

Share this story

Latest stories

More in this category

Latest stories

Explore the TSN Atlas: Every topic we cover, mapped. Click a bubble to dive in.