Logging Tool Flaw Drains 1.58 Million USD From Fluidkey Privacy Wallets in 36 Minutes

Hackers drained at least 1.58 million USD from users of the privacy-focused crypto wallet Fluidkey on November 19, 2026, after exploiting a flaw in an outside logging service to slip unauthorized transfers into the app.
By Marcus Reid | November 21, 2026
For everyday investors, the breach is a sharp reminder that keeping your own private keys—the secret passwords that prove you own your crypto—does not protect your money if an app's back-end servers can queue up transfers behind the scenes. Most of the stolen funds were dollar-pegged stablecoins held by regular users across popular low-fee networks, and Fluidkey has not yet announced a formal reimbursement plan.
Table of Contents
The Incident
The drain unfolded at machine speed on November 19, 2026. According to blockchain analytics firm Bitquery and incident trackers at DeFiLlama, the attacker emptied user accounts across a concentrated 36-minute window running from 17:28 to 18:04 UTC.
Half of the total haul left user wallets within the first five minutes. By 18:05 UTC, Fluidkey detected the abnormal outflows and pulled the plug on its website, mobile applications, APIs, and transaction servers, warning customers to stay away from the platform immediately.
Fluidkey markets itself as a self-custodial privacy wallet—meaning it works like a personal safe where only you hold the master key, rather than a bank holding deposits for you. To hide transactions from public snooping, the app uses stealth addresses, which act like one-time drop boxes for incoming payments, paired with Safe smart accounts, which are programmable digital vaults.
- Total stolen — at least 1.58 million USD across six blockchains, mostly in dollar-backed stablecoins, according to The Defiant and Bitquery.
- Heaviest hit network — users on Base lost approximately 837,000 USD.
- Second-largest loss — accounts on Ethereum lost approximately 660,000 USD.
- Other affected chains — smaller drains hit user funds on Arbitrum, Optimism, Polygon, and BNB Chain.
- Attack speed — the core theft took 36 minutes, with half of the stolen money gone in the first five minutes.
Following the Money
Once the unauthorized transfers cleared user accounts, the attacker wasted no time scrubbing the trail. Forensic tracking by Bitquery shows the stolen stablecoins and tokens across the six networks were consolidated into six separate attacker wallets and converted into Ether.
From there, the thief funneled 881.6 ETH—valued at roughly 1.57 million USD at the time of the transfers, according to Bitquery—into Tornado Cash. Tornado Cash is a crypto mixer, a service that works like a digital blender by pooling deposits from many users so outside observers cannot easily trace which coins went where.
Moving funds into a mixer within minutes sharply reduces the odds of a quick freeze or clawback. While centralized stablecoin issuers can sometimes blacklist stolen tokens sitting in visible wallets, once those assets are swapped for Ether—which trades at 1,685 USD today—and pushed through a mixer, investigators face a much harder recovery path.
The Weak Point
Many crypto breaches happen because a bug sits inside the public code that holds funds on a blockchain. In Fluidkey's case, the broken lock sat in a routine piece of background software rather than on the blockchain itself.
In disclosures covered by The Defiant and Cryptopolitan, Fluidkey traced the breach to vulnerabilities inside a third-party logging tool—essentially an outside record-keeping desk that apps use to monitor performance and errors. By exploiting that logging software, the attacker harvested live session data, the digital check-in passes that keep a user logged in.
Armed with that session data, the attacker targeted Fluidkey's relayer service. A relayer acts like a courier service: it packages a user's crypto transfer and pays the network transaction fee up front so the user gets a smooth, gas-free experience.
The attacker used those stolen session passes to stage unauthorized payout requests on Fluidkey's own servers. Whenever an unsuspecting customer opened the app during that 36-minute window, the software automatically triggered and signed the pre-staged transfers sitting in the queue.
Fluidkey stressed that users' underlying private keys never left their local phones or computers. Even so, the distinction offers cold comfort to victims: if an app's server-side workflow can slip a rigged withdrawal slip under your thumb the instant you open the screen, local key storage alone cannot stop the loss.
How the Industry Responded
After shutting down its web portal, mobile apps, APIs, and relayers at 18:05 UTC on November 19, Fluidkey called in outside help. According to CryptoSlate and Bitquery, the team teamed up with SEAL 911—an emergency volunteer hotline staffed by blockchain security responders—to trace the stolen funds and lock down the compromised workflow.
Between November 20 and November 21, Fluidkey restored service alongside a mandatory software patch, version 1.79.22, across web, iOS, and Android. The update permanently blocks older versions of the app from sending funds and closes the server-side transaction staging path that the attacker abused.
Users who want to move funds again must update to v1.79.22 inside their app settings, as every prior release remains cut off. Fluidkey has promised a full technical post-mortem report and says it is reaching out to impacted account holders individually, though it has not announced a formal compensation or refund program.
Meanwhile, security analysts and reporting from CryptoTicker have warned victims to watch out for a second wave of theft. Scammers are already circulating fake refund and compensation links on social media and in direct messages, hoping panicked users will connect their wallets to another trap.
Lessons for Your Wallet
The Fluidkey drain highlights a blind spot that trips up many retail investors: self-custodial does not automatically mean independent. Whenever a wallet relies on company servers for logins, fee payments, or privacy routing, a flaw in an outside vendor can still put your balance at risk.
- Check for forced updates — if you use Fluidkey, verify you are running version 1.79.22 through official app channels before approving any transfer.
- Ignore unsolicited refund links — legitimate wallet teams do not distribute reimbursement forms through random direct messages or social media replies.
- Separate spending cash from savings — keep everyday trading stablecoins in a hot wallet, and store long-term holdings in an offline hardware wallet that requires a physical button press for every transaction.
- Question automatic approvals — convenience features that hide network fees and signing prompts remove the pause that lets you spot a bad transfer before it leaves.
Marcus Reid's take
Self-custody breaks down the moment a remote server can stage a transfer behind a user's back. What Fluidkey's promised post-mortem reveals—and whether a reimbursement plan recovers that 1.58 million USD loss—matters far more to me than shipping version 1.79.22 after the drain. Mandatory device-level confirmation screens showing every destination address before a relayer fires would earn back my trust in gasless privacy apps.
The cryptocurrency market remains highly volatile. This article is for informational purposes only and does not constitute financial advice.
2 Comments