
On 24 December 2025, a malicious version (2.68) of the Trust Wallet browser extension was published to the Chrome Web Store. It drained funds from users' wallets. This page is a plain summary of what happened, based on Trust Wallet's own incident update and press coverage, plus what to do if you used the extension.
Quick facts (from Trust Wallet's update)
- Affected: the Trust Wallet browser extension, version 2.68. Trust Wallet said its mobile app and other extension versions were not affected.
- Timeline: the tampered version was published on 24 December 2025. The affected window was 24 to 26 December, and the first drains were reported on 25 December.
- Fix: Trust Wallet rolled back to a verified clean build (2.67) and released it as 2.69. It also said a verification tool was planned for 2.70.
- Losses: Trust Wallet cited about $8.5 million in assets impacted, linked to 17 attacker-controlled addresses, and 2,520 wallet addresses identified as drained. Early press reports said about $6 to $7 million, so the figure grew as the investigation went on.
- Claims: Trust Wallet said it had received more than 5,000 reimbursement claims, many of them likely duplicates or fraudulent.
What went wrong
According to Trust Wallet, the attacker got hold of the extension's source code and the Chrome Web Store API key. It said these came from developer secrets exposed in the November 2025 "Sha1-Hulud" supply-chain incident. With that key, the attacker uploaded a tampered build, which skipped the company's normal internal review. Trust Wallet said its investigation was continuing.
This is called a supply-chain attack: instead of hacking each user, the attacker compromises the software update that users trust. Some early reports named specific files and a domain used to send out stolen data, but I have not repeated those details here because I could not verify them from the official update.
What to do if you used the extension
- Check whether you were exposed. Trust Wallet said users who used version 2.68 and logged in during 24 to 26 December 2025 may be at risk.
- Move your funds from any at-risk wallet to a newly created wallet, preferably a hardware wallet, from a clean device. A wallet whose recovery phrase was exposed cannot be made safe again.
- Update the extension from the official Chrome Web Store listing to the latest version.
- Claim reimbursement only through the official support form that Trust Wallet links from its incident page.
- Review token approvals on your wallets. See my guide on revoking wallet approvals.
Lessons for wallet users
- Browser extensions are hot wallets. They sit on a device that is online, so keep only spending money in them.
- Keep large holdings on a hardware wallet and confirm every transaction on its screen.
- Do not update in a rush, or ignore a sudden update. Check official channels for release news before you install or approve a wallet update, especially one that arrives around holidays.
- Use a separate browser profile for your wallet, with few other extensions.
- Know that self-custody wallets have no password reset or 2FA that can bring back stolen funds. If someone gets your keys, the funds can be gone.
If you are new to Trust Wallet, read my airdrops and safety page before you connect your wallet to anything. For a comparison of wallet types, see my best crypto wallets in Nigeria guide.
Frequently asked questions
Was the Trust Wallet mobile app affected?
Trust Wallet said the mobile app and other extension versions were not affected. Only browser extension version 2.68 was.
Will users be reimbursed?
Trust Wallet said it is voluntarily reimbursing affected users through case-by-case review. When I read its update, the process was still being finalised and no payouts were confirmed there. Check the official page for the current status.
Is Trust Wallet safe to use now?
No wallet is risk-free. The company rolled back the bad build and planned extra checks. The practical lessons are the same as before: use official sources, keep large amounts offline and never share your recovery phrase.
How did the attacker get in?
Trust Wallet said it was through leaked developer secrets, including a Chrome Web Store API key, linked to the earlier Sha1-Hulud incident. This is the company's account, and its investigation was ongoing.
This post is a news summary and not financial or security advice. Read my disclaimer.
Sources: Trust Wallet incident update; CoinDesk; The Hacker News; The Block.
Written by EnatDigital
Comments
Post a Comment