Fluidkey restores service and links the attack to exposed session data

Fluidkey relaunched with version 1.79.22. Bitquery estimates at least $1.58 million was drained in the 19 November incident.

Current status: Attack contained

At publication

Affected partyFluidkey
Event dateNovember 19, 2026
NetworkBase, Arbitrum
Status reported by sourceAttack contained
Estimated loss≥ $1,580,000
FrozenNo confirmed data
ReturnedNo 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

  1. Follow-upAttack contained

    Fluidkey restores service and links the attack to exposed session data

  2. First publicationAttack contained

    Fluidkey pauses services after unauthorized user transactions

Source report:

Sources

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

Submit an application

Leave a request

How to contact you?

Specify Telegram username or email — depending on the chosen method of communication.