Fluidkey Says Unpatched Logging Tool Let Attacker Take $1.6 Million
The privacy wallet's post-mortem says stolen session tokens hit 52 accounts, and 17 bank account numbers and 54 viewing keys were also exposed.

Fluidkey said Saturday evening that an attacker took about $1.6 million from 52 user accounts on Nov. 19 by using two known flaws in a logging tool the wallet ran on its own servers.
The post-mortem says the attacker also pulled personal data tied to 70 accounts, including 17 bank account numbers, plus the viewing keys of 54 new accounts. Fluidkey said users' private keys never left their devices.
How the transfers went through
Fluidkey is a privacy wallet that sends each incoming payment to a fresh address. A viewing key shows those addresses, balances and history, but can't move money.
The report says the open-source logging tool, SigNoz, had stored users' session tokens, the codes that tell a server someone is logged in. With them, the attacker created transfer requests on Fluidkey's servers, marked them approved and raised two-factor spending limits. Small payments then set off app notifications. When a user opened and unlocked the app, it signed the waiting transfer as if the user had approved it.
The fixes were two months old
Fluidkey ran SigNoz version 0.121.1. SigNoz published advisories on Sept. 14 and Sept. 17 for a missing login check and a database-query injection flaw (fixed in versions 0.141.1 and 0.142.1). The report says the attacker read the logs from Nov. 12 to Nov. 19.
Where the money went
The transfers ran from 12:28 p.m. to 1:05 p.m. ET on Nov. 19 across six networks, including Ethereum and Base. Fluidkey said most funds were swapped to ETH and about 887 ETH went into a mixing service, which pools coins to hide their trail. It hired tracing firm zeroShadow and reported the case to the FBI and Swiss cyber authorities. CyberSIXT and The Defiant also reported the findings.
The wallet returned Nov. 20 with version 1.79.22. Its servers now accept a transfer request only when the user signs it, and tokens are no longer logged. The report doesn't say whether users will be repaid.
In our opinion: The private keys stayed on users' devices and the money still left, because the app signed what the server put in front of it. Fluidkey's new rule, that the user must sign each transfer request, closes that gap. For the 52 account holders, repayment is the open question. Fluidkey says it will update the report as the investigation develops, and that update is the document to watch.
Sources: Fluidkey: Security incident report, 19 November 2026 · Fluidkey on X: Post-mortem announcement · SigNoz GitHub advisory GHSA-v549-7j2x-qjm5 · SigNoz GitHub advisory GHSA-w5pf-xwjh-vr5v · CyberSIXT: Fluidkey hack, $1.6M stolen via session tokens in SigNoz logs · The Defiant: Fluidkey says unpatched tool enabled $1.6 million hack · ChainCatcher: Fluidkey disclosed the reason for the theft
Revisions
First published .
No revisions since publication.
We fix errors and say so. See every correction on the Blackmint corrections page.