browser extension

The Trust Wallet Browser Extension Supply Chain Attack

Updated 5 Oct 2026 · Incident date 24 Dec 2025

Trust Wallet browser extension 2.68 stole seed phrases from users who unlocked their wallet, in December 2025.

Version 2.69 is the fix. The attackers used a leaked Chrome Web Store API key to upload the build. They did not break into the source repository.

What happened

An unauthorized build of version 2.68 reached the Chrome Web Store on 24 December 2025.

  • Trust Wallet says the build was published outside its release process, with an API key that leaked in the Shai-Hulud campaign of November 2025.
  • In 8423.js, new code read the decrypted seed phrases after a user unlocked the wallet.
  • It stored them in a variable named errorMessage.
  • In 4482.js, the PostHog settings pointed to api.metrics-trustwallet.com.
  • The code packed the seed phrases into analytics events, compressed them with GZIP and sent them by HTTP POST. The attacker controls that domain.

The attack domain was registered on 8 December 2025. The release went out at 12:32 UTC on 24 December. Users who logged in before 11:00 UTC on 26 December were at risk.

Affected versions

  • Trust Wallet Browser Extension 2.68. Version 2.67 was the clean release before it.
  • Fixed in 2.69.
  • At risk: any user who unlocked the wallet while 2.68 was installed. Trust Wallet places the incident between 24 and 26 December 2025.

Indicators of compromise

  • Domain: metrics-trustwallet.com.
  • Subdomain: api.metrics-trustwallet.com. It receives GZIP-compressed analytics events.
  • Changed files in the extension: 8423.js and 4482.js.
  • A variable named errorMessage that holds decrypted seed phrases in 8423.js.

How to check

Open the extensions page in Chrome and read the Trust Wallet version. You can also search the extension files for the attack domain. This command works on macOS. On Linux, use ~/.config/google-chrome.

grep -rl "metrics-trustwallet" ~/Library/Application\ Support/Google/Chrome/*/Extensions/ 2>/dev/null

What to do now

  1. Update the extension to 2.69 or later.
  2. If you unlocked the wallet on 2.68, move your funds to a new wallet with a new seed phrase.
  3. Check wallet history for transfers that you did not start. The attacker emptied wallets from 25 December 2025.
  4. Submit a claim only through the official Trust Wallet support site. Trust Wallet says it never asks for private keys.

Frequently asked questions

How much was stolen?

Trust Wallet reports about 8.5 million US dollars across 2,520 verified wallet addresses. The Hacker News reports about 7 million US dollars and 2,596 wallets.

Will Trust Wallet reimburse users?

Trust Wallet says it will reimburse affected users. It received more than 5,000 claims, including fraudulent ones.

Sources

  1. trustwallet.com/blog/announcements/trust-wallet-browser-extension-v268-incident-community-update
  2. blocksec.com/blog/trust-wallet-incident-a-stolen-api-key-turns-the-official-update-channel-into-a-backdoor
  3. thehackernews.com/2025/12/trust-wallet-chrome-extension-bug.html

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library