Fluidkey Discloses $1.6M Exploit: A Wake-Up Call for Self-Custody Wallets
TREE NEWS reports: Fluidkey, a self-custodial crypto wallet, has revealed the root cause of a security breach that resulted in the theft of approximately $1.6 million from 52 user accounts. The incident, which occurred earlier this week, was traced to vulnerabilities in its self-hosted logging tool, SigNoz, which allowed attackers to access internal logs and obtain user session tokens.
How the Attack Unfolded
The attackers exploited two flaws in SigNoz to read internal logs. With the stolen session tokens, they were able to create and approve transfer requests, raise two-factor authentication payment limits, and trigger notifications via small transfers. When users opened and unlocked the app, the application signed pre-prepared unauthorized transactions. Crucially, the private keys controlling the funds never left users’ devices, highlighting that even self-custody solutions are not immune to sophisticated attacks.
Additionally, the attackers accessed view keys for 70 accounts and 54 newly registered accounts. View keys allow visibility into addresses, balances, and transaction history but cannot be used to move funds. Fluidkey has since updated its logging tool, terminated existing login sessions, and strengthened transfer authorization verification. The service was restored on November 20 at 23:27 Beijing time, and the company is working with blockchain investigator zeroShadow to trace the stolen funds.
Industry Implications: The Growing Threat of Session Token Exploits
This incident underscores a broader trend in crypto security: attackers are increasingly targeting the infrastructure that supports self-custody wallets rather than the private keys themselves. Session tokens, which authenticate users during active sessions, have become a valuable target because they can bypass some security measures and enable unauthorized actions without direct key compromise.
For wallet providers, the attack highlights the importance of securing not just the core cryptographic components but also auxiliary systems like logging, monitoring, and authentication. Self-hosted tools, while offering control and privacy, can introduce vulnerabilities if not properly configured and patched. The use of third-party or open-source logging solutions requires rigorous security audits and continuous monitoring.
Moreover, the exploit demonstrates that two-factor authentication and payment limits can be circumvented if session tokens are compromised. This suggests that wallets need to adopt more robust session management, such as short-lived tokens, device binding, and anomaly detection.
Forward-Looking Perspective: Strengthening the Self-Custody Stack
As the crypto industry matures, the bar for security will continue to rise. Fluidkey’s response—updating the logging tool, terminating sessions, and enhancing authorization—is a necessary first step, but it may not be enough to restore user confidence. The company must conduct a thorough post-mortem and consider a broader security overhaul, including penetration testing and bug bounty programs.
For the wider ecosystem, this incident serves as a reminder that self-custody is not just about holding your own keys; it’s about securing every layer of the stack. Wallet providers should prioritize security audits of all components, including logging and monitoring tools, and adopt a zero-trust approach to session management. Users, meanwhile, should remain vigilant and enable additional security features where available.
Ultimately, the Fluidkey exploit is a cautionary tale: in the quest for decentralization, we must not overlook the security of the infrastructure that makes it possible. As attackers grow more sophisticated, the industry must stay one step ahead.




