What happened
Attackers drained at least $1. 58 million from wallets linked to Fluidkey, a stealth-address wallet product built on EIP-5564 style primitives, according to on-chain analytics firm Bitquery. CryptoSlate first reported the breach on Friday at roughly 02:30 UTC, citing Bitquery's trace of the incident-linked addresses across six chains.
Bitquery flagged that not every outflow is necessarily malicious. Some transfers from the clustered set look like ordinary user withdrawals, the firm said, which means the final tally could move as the trace is refined. The specific attack vector has not been disclosed in detail by Fluidkey as of publication.
What is clear is that the compromise did not require the attacker to hold a user's private key. Fluidkey's architecture generates stealth addresses locally, with keys stored on the user's device, so the breach points to something other than classic seed-phrase theft.
Why it matters
Fluidkey's pitch to users was simple. Keys stay on your device, so no central custodian can be hacked to drain you. Friday's incident doesn't disprove that claim in the literal sense, but it punctures the marketing halo around it.
Client-side key custody is not a complete threat model. Session tokens, relayer permissions, meta-transaction signatures, and the browser or extension layer that assembles transactions are all attackable surfaces that sit upstream of the private key itself. The sector has spent two years selling account abstraction and stealth-address privacy as safer defaults for regular users.
Friday's $1. 58 million is a reminder that "keys never leave your device" is one bullet point in a long list, not a guarantee. Expect the usual chorus of audit calls and bug-bounty expansions in the next 48 hours.
