Meta Force Space
BTC $60,280.00 +2.69% ETH $1,684.76 +4.88% SOL $70.70 +3.45% XRP $0.9367 +4.24% BNB $549.67 +2.64% DOGE $0.0553 +3.57%
← Back to the news

Fluidkey’s $1.6 million hack exposes a security risk even when private keys never leave users’ devices

Quick Take

  1. Fluidkey says it restored its web, iOS and Android apps and requires version 1.79.22 before users can send funds.
  2. Bitquery traced at least $1.6 million to incident-linked wallets across six chains and identified a likely user withdrawal.
  3. Users can check transfers and balances at known addresses while Fluidkey prepares to contact affected users individually.

Fluidkey said it restored its privacy wallet on Nov. 20, a day after taking it offline following unauthorized transfers.

Sending funds requires an app update, and users who spot an unfamiliar transfer can look up their own receiving address or transaction hash on the relevant blockchain.

The company announced the return of its web, iOS, and Android apps in v1.79.22. It said older versions would stay offline and told users to open Settings and select Update to re-enable transactions.

Fluidkey attributed the incident to flaws in a third-party logging tool and said users’ private keys stayed on their devices, and said it took services offline on Nov. 19. In its update that evening, it said it had seen no further unauthorized transactions since the shutdown and was working with SEAL 911 to investigate and trace funds.

Its initial warning to avoid the site and app came before the new version was available.

Blockchain analytics firm Bitquery traced roughly $1.6 million in payouts to wallets it linked to the incident across six chains, including Base and Ethereum.

The independent Fluidkey drain tracker, maintained by pepebndc, put the total near $1.63 million across seven chains in its Nov. 20 morning snapshot. That estimate includes suspected destinations and excludes likely owner withdrawals.

Bitquery says the tracker labeled one Polygon payout as an owner withdrawal, linking it to the incident after following the recipient’s activity on Base.

The firm also separated the incident-linked payments from about $349,000 sent to wallets with an established history during its hour-long scan.

That group includes ordinary payments before the drain and about $277,000 sent during it to an older wallet across Ethereum and Base. Bitquery interpreted the latter as one user moving their own funds, and left another $65,000 unclassified.

Where Fluidkey’s payouts went

Bitquery’s six-chain scan, Nov. 19, 17:10 to 18:10 UTC.

Bitquery’s estimate covers the wallets it linked to the incident. Other payouts included apparent user transfers.

Bitquery inferred ownership from wallet activity. The $349K includes ordinary payments before the drain. Unclassified payouts could include incident-linked funds.

Sources and evidence

Sources

  1. Bitquery’s six-chain investigation

Supporting facts

  • Bitquery attributed at least $1.58 million in payouts to wallets it linked to the incident across six chains between 17:28 and 18:04 UTC on Nov. 19. [1]
  • In a six-chain scan from 17:10 to 18:10 UTC on Nov. 19, Bitquery counted about $349,000 going to wallets with an established history and $65,000 going to destinations it could not classify. The $349,000 includes ordinary transfers before the incident and movements consistent with users transferring their own funds. [1]
  • Bitquery identified roughly $277,000 sent during the incident to an older wallet in a transfer pattern it interpreted as one user moving their own funds across Ethereum and Base. [1]

Method

Bar lengths use Bitquery’s published rounded USD category values on one zero-based scale. The shaded part of the prior-history bar marks about $277,000 within the $349,000 group, which Bitquery interpreted as one user moving funds.

Scope

Bitquery inferred ownership from wallet activity. The $349K includes ordinary payments before the drain. Unclassified payouts could include incident-linked funds.

Infographic by CryptoSlate

What FluidKey users can check now

If you have a receiving address or transaction hash, look it up in a block explorer for the relevant chain. The ethereum.org guide to block explorers explains how those records are organized.

Compare the time, amount, and destination with your own records and check the balance at your known address. The chain records the transfer, but the record alone cannot establish who authorized it.

Fluidkey’s standing recovery guide describes SARA as a last-resort option for verifying addresses or accessing funds. It warns that moving funds outside the regular app may impair app functionality.

In its incident update, Fluidkey said it would contact affected users individually and publish a full post-mortem. It warned about impersonation and said its staff would never contact users privately through social media, and directed users to its official website for support.

Editorial credits

Liam 'Akiba' Wright
Liam 'Akiba' Wright
Editor-in-Chief CryptoSlate

Also known as "Akiba," Liam Wright is a reporter, podcast producer, and Editor-in-Chief at CryptoSlate. He believes that decentralized technology has the potential to make…

Gino Matos
Gino Matos
Reporter CryptoSlate

Gino Matos is a law school graduate and a seasoned journalist with six years of experience in the crypto industry. His expertise primarily focuses on the Brazilian blockchain…

Originally published by CryptoSlate on

Read the original on CryptoSlate ↗

Text and images are the property of CryptoSlate and are reproduced here with attribution and a link to the original publication.

More stories

All the latest news