Trust Wallet’s Chrome extension shipped a malicious update in December, exfiltrating wallet data and draining roughly $7 million from hundreds of accounts before the company pushed a fix.

The compromised version 2.68 was live for days, auto-updating in the background, the way browser extensions are designed to. Users who followed every standard self-custody rule, such as never sharing their seed phrase, checking URLs, and using reputable wallets, still lost funds.

The attack targeted the browser layer, not the blockchain, and it exposed a persistent trade-off that the industry has spent years trying to ignore: browser-extension wallets are always-on hot wallets sitting in one of the most hostile environments in computing.

This wasn’t an isolated case. MetaMask’s security team documented a fake Google Chrome extension called “Safery: Ethereum Wallet” that lived in the official Chrome Web Store from late September until mid-November, stealing seed phrases.

Chainalysis estimates that crypto theft reached $3.4 billion in 2025, with personal wallet compromises accounting for 20% of that total, or $713 million. However, that would have been 37% without the Bybit exchange hack.

For perspective, personal wallet compromises accounted for just 7.3% of the stolen value in 2022 and 44% in 2024, indicating that attackers are following the value to wherever user keys live.

Personal wallet compromises reached 44% of total crypto losses in 2024 before dropping to roughly 23% in 2025 as service losses increased

Where the attacks actually happen

The weak links in 2025 are almost all “above” the chain, such as browser, extensions, and supply chain, while most user education still focuses on what happens below, at the private key and seed storage level.

The attack paths break down into four layers.

A diagram shows the attack surfaces for crypto users, with over 20% of 2025 exploits targeting browser and wallet extension layers above the blockchain.

The browser and OS layer is where info-stealer malware operates. Families like ModStealer, AmosStealer, and SantaStealer infect the machine, read extension storage, intercept keystrokes, or hook browser APIs to capture seeds and private keys at rest.

The browser is the entry point, and extensions are the payload.

The wallet extension layer is where compromised or malicious updates operate. Trust Wallet’s version 2.68, the fake “Safery” wallet, and the malicious wallets on Chrome all added code that exfiltrated secrets or tampered with transaction requests before users saw them.

This is the UX and supply-chain trade-off in action: auto-updates are critical for patching vulnerabilities, but they also deliver bad code at scale when the update mechanism itself is compromised.

The dApp and connector layer is where libraries like Ledger Connect Kit get hijacked. When these are compromised upstream, legitimate dApps start presenting malicious transactions.

The user connects their real wallet or hardware device, sees a normal-looking prompt, and signs a drainer transaction. This layer is invisible to most users, as they don’t know which JavaScript libraries power the dapps they use, and they have no way to verify that those libraries haven’t been tampered with.

The RPC and blockchain layer is where the attack completes. Once a malicious transaction is signed and broadcast, the rest of the stack works as designed.

Funds move, and the only remaining defenses are monitoring, rapid incident response, and any off-chain recovery measures the ecosystem might have. By this point, the damage is done. The blockchain didn’t fail, but the layers above it did.

The industry knows the problem and hasn’t fixed it

The Trust Wallet incident, the fake Chrome extensions, the Ledger Connect Kit exploit, and the rising share of personal wallet compromises all point to the same conclusion: the browser is a hostile environment, and “self-custody best practices” around seed phrases and hardware still don’t fully address that.

The failure mode has shifted from users mishandling keys to attackers compromising the UX layer, and the industry has known this for years.

The architecture hasn’t changed because the alternatives are either too cumbersome for mass adoption or too centralized to fit the ethos.

Until browser wallets can be isolated from the broader browser environment, or until transaction signing happens in a truly air-gapped flow that doesn’t rely on JavaScript libraries and auto-updating extensions, the trade-off will persist.

Users can follow every rule, use hardware wallets, never share their seeds, and still lose funds because the code they’re interacting with, and which they have no practical way to audit, has been silently compromised.

That’s not a user-education problem. It’s an architecture problem and no amount of “best practices” will fix it.