Fluidkey hack: $1.6M stolen via session tokens in SigNoz logs
Part of the CVE-2026-92729 story · since 22 Nov
- Sun 22 Nov, 01:55 UTC. cybersixt, first report. Fluidkey hack: $1.6M stolen via session tokens in SigNoz logs. This article, 1st of 1.
Crypto wallet app Fluidkey says an attacker stole about $1.6 million from 52 user accounts on November 19 without ever touching the private keys that control the funds. In a post-mortem published early on Sunday, the company traces the theft to two known, unpatched flaws in SigNoz, an open-source logging tool it ran on its own servers, which let the attacker read internal logs that held users' session tokens.
The unauthorised transfers ran from 17:28 to 18:05 UTC, when Fluidkey took transaction processing offline. The service came back on November 20 at 15:27 UTC with version 1.79.22. Fluidkey says it has contacted every affected user, and it has reported the incident to the FBI's Internet Crime Complaint Center and to Switzerland's National Cyber Security Centre.
How the attacker got in
The attacker exploited two SigNoz vulnerabilities to read Fluidkey's internal logs between November 12 and 19, after probing the same endpoints from November 5 without getting any log content back, according to the post-mortem. Fluidkey's installation ran SigNoz v0.121.1.
Both flaws had been public for two months. CVE-2026-92729 (GHSA-v549-7j2x-qjm5), published by SigNoz on September 14, is missing authentication on trace-funnel analytics endpoints, rated high with a CVSS score of 8.2 and fixed in v0.141.1. CVE-2026-93292 (GHSA-w5pf-xwjh-vr5v), published on September 17, is an authenticated ClickHouse SQL injection in the same endpoints, rated 7.6 and fixed in v0.142.1. Both affect SigNoz from v0.88.0.
Some Fluidkey services had written users' session tokens to those logs, and the logs also held the viewing keys of some newly registered accounts.
How the theft worked without the keys
The private keys that move funds stay on each user's device, so the attacker could not sign transfers. Instead, Fluidkey says, the attacker used the stolen session tokens to create transfer requests on its servers, mark them as approved and raise the accounts' two-factor spending limits. It then sent small payments to trigger notifications. When a victim opened and unlocked the app, the app signed the prepared transfer as if the user had approved it.
The funds were taken on Ethereum, Base, BNB Chain, Polygon, Optimism and Arbitrum. With the help of SEAL 911, Fluidkey traced most of them as they were swapped into ETH, and says about 887 ETH went into a mixing service on the evening of November 19. Blockchain investigations firm zeroShadow is still tracing the funds.
What else was exposed
From the logs, the attacker also retrieved 38 email addresses, 37 names, 17 bank account numbers (IBANs), 24 postal addresses, four dates of birth and two phone numbers relating to 70 accounts, plus the viewing keys of 54 new accounts. A viewing key shows an account's addresses, balances and transaction history but cannot move funds. Fluidkey says it is notifying the relevant data protection authorities.
What Fluidkey changed
Before going back online, Fluidkey ended all sessions, updated SigNoz to a fixed version, rotated its credentials and took its query interface off the public internet. Its servers now accept a transfer request only if it is authorised with the user's own key, so a session token alone can no longer create and approve one, and changes to two-factor limits are verified on the server. It says session tokens and sensitive data are no longer written to logs, and that it is reviewing every third-party and self-hosted tool it runs, including how it learns of security advisories.
On November 19 Fluidkey had promised a full post-mortem once its investigation was complete. The company says the investigation is still ongoing and that it will update the report as its findings develop.
How the story developed
1 article from 1 outlet since 22 Nov. Still developing; the latest report was 46 minutes ago. This was the first report.
- Sun 22 Nov, 01:55 UTC. cybersixt, first report. Fluidkey hack: $1.6M stolen via session tokens in SigNoz logs. This article, 1st of 1.
- CVE not in KEV
- No CVE
- Larger: an outlet’s first report
- Coverage over time
Show all 1 articles as a listHide the list
- Sun 22 NovDay 01
- Fluidkey hack: $1.6M stolen via session tokens in SigNoz logs01:55 · cybersixt · First report · This article, 1st of 1
Sources
- Fluidkey: Security incident of 19 November 2026Primary sourcedocs.fluidkey.com
- Fluidkey on X: post-mortemPrimary sourcex.com
- Fluidkey on X: 19 November updatePrimary sourcex.com
- SigNoz advisory GHSA-v549-7j2x-qjm5github.com
- SigNoz advisory GHSA-w5pf-xwjh-vr5vgithub.com
- CyberSIXT CVE-2026-92729cybersixt.com
- CyberSIXT CVE-2026-93292cybersixt.com
More reporting
- GoFundMe data breach: nonprofit donor data accessed via API21 Nov
- iTerm2 vulnerability: cat on a crafted file runs commands21 Nov
- Upload2Shell: Ghostscript CVE-2026-125396 lets uploads run code21 Nov
- GL.iNet GoodCloud flaw used to plant malware on routers, KVMs21 Nov
- FBI hacked again as NCIC crime database is breached21 Nov
Written by CyberSIXT from the sources above.How we reportCorrectionsRSS