Fluidkey Urges Users to Avoid Website and App After Incident
- Published
- Updated
Fluidkey said it was investigating a security incident affecting users and told people to avoid its website and app. The wallet later tied the Nov. 19 drain to flaws in a third-party logging tool and said private keys stayed on users’ devices. Bitquery said it traced at least $1.58 million in transfers connected to the incident.
Key claims & sources
What it means
Fluidkey is a privacy-focused wallet, so this incident sits in a part of crypto where users expect self-custody and minimal data exposure. The company’s note and follow-up explanation point to a wallet that depends on client-side key control while also using outside infrastructure for logging and app operations. That combination makes this a test of how much trust users place in software layers around the wallet itself.
For people using Fluidkey, the immediate effect is uncertainty about account safety and the need to avoid the product until the company finishes its review. The notice did not say whether funds had been lost, and the later statement focused on the route the attacker used rather than on a user-side key compromise. Anyone building wallet software will have to treat logging, session handling, and app access as security-critical parts of the stack, not just the key store. (per thedefiant.io)
The bigger issue is the tension between convenience features and the security model that underpins crypto wallets. A wallet can keep private keys on-device and still expose users if other services around it can be abused to trigger transfers or reuse session data. That leaves the industry with a familiar but uncomfortable trade-off: richer app tooling can expand the attack surface even when custody design stays unchanged. (per thedefiant.io)
Market reaction i
The total crypto market fell 1.6% in the 4 hours after the first headline, after rising 1.3% in the 2 hours before.
47 prices, one every 30 minutes
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Thefts of a similar size
| When | What happened | Figure |
|---|---|---|
| 2.6 years ago | Pike V1 · Proxy Upgrade Hijack incident | $1.6M |
| 2.9 years ago | INX · Third-party vulnerability incident | $1.6M |
| 3.7 years ago | Tender.fi · Oracle attack incident | $1.6M |
| 6 months ago | Token of Power · Malicious Proposal incident | $1.6M |
| 3.1 years ago | Ivy · Rug pull incident | $1.6M |
4349 incidents stored · 812 were as large as this one or larger ($1.6M)