At publication
| Affected party | Fluidkey |
|---|---|
| Event date | November 19, 2026 |
| Network | Base, Arbitrum |
| Status reported by source | Attack contained |
| Estimated loss | ≥ $1,580,000 |
| Frozen | No confirmed data |
| Returned | No confirmed data |
What happened
Fluidkey announced its return on 20 November with version 1.79.22 for web, iOS and Android, while blocking older versions. The project attributes the incident to a third-party logging tool that exposed session data.
According to the team, this allowed unauthorized transfers to be prepared on its servers and signed when users opened the app. Fluidkey says private keys remained on users’ devices; this is the project’s account, pending a full incident report.
Bitquery traced at least $1.58 million to attacker-linked flows across six networks. That is a research estimate rather than a company-confirmed total. Restored service does not establish completed refunds; the reviewed sources provide no confirmation of reimbursement.
Incident history
Source report:
Sources
- Fluidkey — service restored and incident explanation — Original source · x.com · November 20, 2026
- Bitquery — attacker-linked fund flows — Analysis · bitquery.io · November 20, 2026
- Coindaro — statement and research cross-check — Report · www.coindaro.com · November 21, 2026
Information is attributed to the linked sources and has not been independently verified by Match Systems. Loss estimates and incident status may change as new evidence becomes available.
Latest incidents
- ExploitElliptic traces at least 2,310 BTC from the Binance theft through coinjoins
- Under investigationXMR1 operator attributes key exposure to a hosting breach and promises refunds
- Under investigationAbout $1.51 million leaves retired OCEAN pools; circumstances remain unclear
- Under investigationChainflip halts swaps after an estimated $4.86 million vault drain
- ExploitLookonchain tracks another 137,602 ETH from Binance-linked hack wallets
- Under investigationXMR1 faces suspected security incident after deployer transfers