Fluidkey acknowledged a security incident affecting users on November 19, 2026 and advised users not to interact with its website or app while it investigated. Reports cite a log vulnerabilit
Fluidkey acknowledged a security incident affecting users on November 19, 2026 and advised users not to interact with its website or app while it investigated.
Reports cite a log vulnerability in the $1.6 million theft
ChainCatcher reported that attackers used two SigNoz vulnerabilities to access internal logs, then leveraged session tokens recovered from those logs to initiate unauthorized transfers. PANews reported that the stolen funds totaled roughly $1.6 million across Ethereum, Base, BNB Chain, Polygon, Optimism, and Arbitrum, making this a multi-chain incident rather than a single-network drain.
The attack was notably fast: within approximately five minutes of the first unauthorized transfer, roughly half of the total stolen amount had already moved, per reporting by CryptoNews.net. The entire drain window ran from 17:28 to 18:04 UTC on November 19, a span of 36 minutes total. The largest single transfer extracted $415,783 USDT from two Ethereum accounts during that window, the same source reported. For related coverage, see Reported $166M USDT Transfer: US Session Roundup.
Fluidkey's official statement on X advised users not to interact with the website or app while the investigation proceeded. The statement did not provide technical details, loss totals, affected-account counts, or service-restoration information; those details in this article are attributed to secondary reporting. Context on this theme: HYPE Holding Near Breakeven: Asia Session Roundup.
Source: @fluidkey on X
Scope of affected accounts and what was exposed
Reports stated that 52 accounts suffered direct financial losses, 70 accounts had personal data exposed, and 54 newly registered accounts had viewing keys compromised. According to those reports, viewing keys permit an observer to see wallet addresses, balances, and transaction histories but cannot authorize fund transfers, meaning the 54 affected new accounts faced a privacy breach rather than a financial one.
CryptoNews.net reported that Bitquery's on-chain tracing placed the total amount reaching attacker-linked wallets between $1.58 million and $1.64 million. The same reporting cited a community-maintained GitHub tracker that placed the total near $1.63 million and said Fluidkey engaged blockchain investigator zeroShadow and notified law enforcement, though no jurisdiction or agency has been publicly named.
Approximately 881.6 ETH, worth roughly $1.57 million at the time, was deposited into Tornado Cash across six attacker-linked wallets between 20:05 and 21:29 UTC on November 19, according to CryptoNews.net's timeline reconstruction. The mixing activity began less than two hours after the drain window closed, suggesting the attacker moved to obscure fund origins before any public disclosure had been made.
Why logs and session tokens are sensitive security assets
Application logging tools like SigNoz are designed to capture request metadata, error traces, and system events to help engineering teams debug production issues. When HTTP request headers, authentication cookies, or bearer tokens are logged verbatim, the log store becomes a secondary credential repository with an attack surface that often receives less security scrutiny than the primary authentication system. Self-hosted observability infrastructure can compound the risk if its own access controls are not hardened to production security standards.
Fluidkey's situation illustrates the asymmetry: the primary wallet security model, in which private keys remain on user devices and are never transmitted to servers, held as designed. What failed was a peripheral infrastructure component that was not designed to be a security boundary but became one by virtue of the data it collected. For builders designing non-custodial wallet infrastructure with server-side relayer components, this incident signals that the security perimeter extends to every system that can observe or store session credentials, not only to the systems that hold private keys. As a prior Bitcoin Core node message processing vulnerability demonstrated, infrastructure components adjacent to core cryptographic logic can carry disproportionate risk when their attack surface is underestimated.
CryptoNews.net reported that Fluidkey restored service on November 20 with version 1.79.22, which reportedly blocks the unauthorized transfer preparation method used through stolen session tokens. The report said users running older app versions remain blocked from the platform until they update and that the company terminated existing active sessions, requiring users to reauthenticate after the patch was deployed.
The company said a comprehensive post-mortem will be published once the investigation is complete. No date has been given for that disclosure. The engagement of zeroShadow for on-chain tracking and the law enforcement referral suggest the response involves both technical recovery efforts and an attempt to identify the attacker, though the speed of the Tornado Cash mixing significantly narrows the practical window for fund recovery through tracing alone.
The incident unfolded against a broader market backdrop of caution: the Crypto Fear and Greed Index stood at 11 out of 100, in Extreme Fear territory, as of the time reporting on the incident circulated.
What to watch next
The concrete near-term milestone is Fluidkey's promised full post-mortem, which will establish whether the two SigNoz vulnerabilities were known CVEs, zero-days, or misconfigurations specific to Fluidkey's deployment. That distinction matters for the broader ecosystem: a known CVE would signal that other teams running self-hosted SigNoz deployments should audit their log data retention policies immediately, while a configuration-specific issue is more contained. Analysis: the incident raises questions about session-layer security obligations for non-custodial wallet infrastructure. The outcome of zeroShadow's on-chain tracing, and whether any of the Tornado Cash-routed funds can be identified through subsequent chain movements, represents the second concrete variable worth monitoring in the weeks ahead.
FAQ: Fluidkey's reported $1.6 million security incident
What did Fluidkey say caused the theft?
ChainCatcher reported that the theft involved two vulnerabilities in SigNoz, a self-hosted logging tool Fluidkey operated internally. According to that report, the vulnerabilities allowed attackers to read internal server logs, from which session tokens for some users were obtained and then used to authorize unauthorized transfers.
What are session tokens?
Session tokens are server-issued credentials that identify an authenticated user during an active browsing or app session. They are distinct from private keys; possessing a session token allows an attacker to act through the application's server-side logic as if they were the legitimate user, without having access to the underlying cryptographic keys that control the wallet's funds at the blockchain level.
Were private keys or seed phrases compromised?
According to reports, private keys controlling the funds did not leave user devices. Those reports described the attack as operating at the session and relayer layer, rather than extracting or replicating cryptographic signing keys.
How many users were affected and across which networks?
Reports stated that 52 accounts suffered financial losses totaling approximately $1.6 million, while 70 accounts had personal data exposed and 54 newly registered accounts had viewing keys compromised. The six affected blockchains were Ethereum, Base, BNB Chain, Polygon, Optimism, and Arbitrum, according to PANews.
What details remain unconfirmed from the available disclosure?
As of this report, specific CVE identifiers or technical parameters of the two SigNoz vulnerabilities have not been disclosed. The full post-mortem Fluidkey has promised has not been published, and no law enforcement jurisdiction or agency has been publicly named. A claim that a 2024 audit by Dedaub had warned that a compromised server could deliver malicious code to reach spending keys was reported by a secondary outlet but has not been confirmed in Fluidkey's own disclosures.
Editorial credits
MA
Mayowa Adebajo
Writer · Coincu
HN
Haruto Nakamura
Editor · Coincu
Monitors published articles around the clock and can correct or withdraw them.
Checked by Coincu QC Team before publishing on November 22, 2026 for headline accuracy, original value and authorship claims: our AI review system checks every article before it goes live, and our editor monitors it after publication. Report an error.
Coincu uses AI for research, drafting and review. Our editorial team is responsible for every article and corrects or withdraws articles when needed. How we review.
Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.
The post Reports Cite $1.6M Fluidkey Theft via Session Tokens was initially published on Coincu.