Article Details
Scrape Timestamp (UTC): 2025-12-26 15:32:18.977
Source: https://thehackernews.com/2025/12/trust-wallet-chrome-extension-bug.html
Original Article Text
Click to Toggle View
Trust Wallet Chrome Extension Bug Drains $7M, Users Urged to Update to Version 2.69. Trust Wallet is urging users to update its Google Chrome extension to the latest version following what it described as a "security incident" that led to the loss of approximately $7 million. The issue, the multi‑chain, non‑custodial cryptocurrency wallet service said, impacts version 2.68. The extension has about one million users, according to the Chrome Web Store listing. Users are advised to update to version 2.69 as soon as possible. "We've confirmed that approximately $7M has been impacted and we will ensure all affected users are refunded," Trust Wallet said in a post on X. "Supporting affected users is our top priority, and we are actively finalizing the process to refund the impacted users." Trust Wallet is also urging users to refrain from interacting with any messages that do not come from its official channels. Mobile-only users and all other browser extension versions are not affected. According to details shared by SlowMist, version 2.68 introduced malicious code that's designed to iterate through all wallets stored in the extension and trigger a mnemonic phrase request for each wallet. "The encrypted mnemonic is then decrypted using the password or passkeyPassword entered during wallet unlock," the blockchain security firm said. "Once decrypted, the mnemonic phrase is sent to the attacker's server api.metrics-trustwallet[.]com." The domain "metrics-trustwallet[.]com" was registered on December 8, 2025, with the first request to "api.metrics-trustwallet[.]com" commencing on December 21, 2025. Further analysis has revealed that the attacker has leveraged an open‑source full‑chain analytics library named posthog-js to harvest wallet user information. The digital assets drained so far include about $3 million in Bitcoin, $431 in Solana, and more than $3 million in Ethereum. The stolen funds have been moved through centralized exchanges and cross-chain bridges for laundering and swapping. According to an update shared by blockchain investigator ZachXBT, the incident has claimed hundreds of victims. "While ~$2.8 million of the stolen funds remain in the hacker's wallets (Bitcoin/ EVM/ Solana), the bulk – >$4M in cryptos – has been sent to CEXs [centralized exchanges]: ~$3.3 million to ChangeNOW, ~$340,000 to FixedFloat, and ~$447,000 to KuCoin," PeckShield said. "This backdoor incident originated from malicious source code modification within the internal Trust Wallet extension codebase (analytics logic), rather than an injected compromised third‑party dependency (e.g., malicious npm package)," SlowMist said. "The attacker directly tampered with the application's own code, then leveraged the legitimate PostHog analytics library as the data‑exfiltration channel, redirecting analytic traffic to an attacker‑controlled server." The company said there is a possibility that it's the work of a nation-state actor, adding the attackers may have gained control of Trust Wallet‑related developer devices or obtained deployment permissions prior to December 8, 2025. Changpeng Zhao, a co-founder of crypto exchange Binance, which owns the utility, hinted that the exploit was "most likely" carried out by an insider, although no further evidence was provided to support the theory.
Daily Brief Summary
Trust Wallet's Chrome extension version 2.68 contained malicious code, leading to a $7 million cryptocurrency theft affecting approximately one million users.
Users are urged to update to version 2.69 immediately to prevent further exploitation and ensure security.
The malicious code extracted mnemonic phrases from wallets, sending them to an attacker's server, facilitating unauthorized access to user funds.
The stolen assets include $3 million in Bitcoin and Ethereum, with funds laundered through centralized exchanges and cross-chain bridges.
Trust Wallet is prioritizing user support and has committed to refunding affected users, while advising caution against unofficial communications.
The incident originated from internal codebase tampering, potentially by an insider, rather than an external dependency compromise.
Speculation exists about potential nation-state involvement, with attackers possibly gaining control over developer devices or deployment permissions.
The breach highlights the critical need for robust internal security measures and vigilant monitoring of codebase integrity.