Action required for users impacted by the Browser Extension v2.68 incident: We identified a limited group of ~36k wallets (0.016% of our user base) still having a compromised wallet(s). All impacted users have already been directly notified via a security incident banner on your

We’ve implemented a new “Migrate assets” feature to help users securely move funds from wallets affected by the Trust Wallet Browser Extension v2.68 security incident to a safe wallet. If you are still using a compromised wallet on the browser extension or mobile app: • update

Action required for users impacted by the Browser Extension v2.68 incident: We’re working with @binance to offer an expedited verification path that may simplify and speed up the reimbursement process for a specific group of affected users. If you deposited funds from your

As part of the reimbursement process, we’ve introduced the Customer Support Verification Code (CSVC) in Browser Extension v2.71.0. To find your CSVC, update your Browser Extension, then go to: 1. Settings 2. Help & Support 3. Customer Service Verification Code. This step helps

The Trust Wallet Browser Extension is now back on the Chrome Web Store. The latest version is 2.71.0. We thank you for your patience while we got this resolved.

Some may have noticed that the @trustwallet Browser Extension is temporarily unavailable on the Chrome Web Store. We hit a Chrome Web Store bug 😢 while releasing a new version that includes a feature to help reimbursement claimants submit verification codes from their extension

Please be aware of impersonators. This is the final tweet of this thread.

7/ Thank you to our community for your vigilance, support, and feedback as we work through this together. We recognize the impact this incident has had on our community and the affected users, and we appreciate your patience as our team continues to investigate and execute the

6/ Security is of utmost importance. In parallel with the investigation, we have actively worked on the following: Incident response We have already implemented additional safeguards and controls surrounding: - Browser extension releases - Release system and tool access -

5/ While our forensic investigation is ongoing, we believe this may represent a new class of software supply chain attacks. We’ll continue sharing updates and hope these findings help the industry better recognize and mitigate similar risks.

4/ We have high confidence that the Browser Extension v2.68 incident is related to the Sha1-Hulud incident, an industry-wide software supply chain attack in November 2025. Our investigation suggests that the malicious build of v2.68 was prepared independently and distributed via

3/ What happened: On Dec 24, 2025 An externally prepared, unauthorized and malicious version of Trust Wallet Browser Extension v2.68 was published to the Chrome Web Store outside our standard release and review process. This version contained malicious code that, when loaded,

2/ We see this incident not only as a critical lesson for Trust Wallet, but as a potential inflection point for the broader industry. As supply chain attacks become more sophisticated and require collective awareness and stronger safeguards.

We’re sharing a work-in-progress update on the Browser Extension v2.68 incident. 1/ Our current hypothesis on how this attack occurred and what this signals for the wider industry. Full details are in the blog:

Browser Extension Incident - Short Update (Dec 28) Here’s where we are with the investigation of the Browser Extension v2.68 incident. 1/ First of all, I want to say we truly recognise the impact this incident has had on our users and the victims, and we appreciate the

Browser Extension Incident - Short Update (Dec 27) Sharing another update on where we are with the Browser Extension incident handling. 1/ Our forensic investigation is ongoing. Google replied saying it has escalated our ticket - good news! We hope to receive the Chrome Store

I want to share a transparent update on the @TrustWallet Browser Extension v2.68 security incident, and what we know so far ~24 hours of the attack. This is an ongoing investigation, so I’ll focus on confirmed facts and updates, highly likely hypothesis, and what we’re doing to

Please be aware of impersonators. This is the final tweet of this thread.