TLDR
A malicious update to Trust Wallets Chrome browser extension (version 2.68) introduced a vulnerability that drained user wallets; upgrading to version 2.69 is the fix per a confirmed report from the team (details).
- Losses are about $7 million, and affected users will be reimbursed (statement).
- Investigators suspect an insider role in how the compromised update passed distribution checks (analysis).
- Reports noted immediate drains when importing a seed into v2.68 (incident summary).
Deep Dive
1. Compromised Version
The issue centers on the Chrome extension update to version 2.68, which the Trust Wallet team confirmed as problematic. Users were advised to avoid v2.68 and upgrade to v2.69, while mobile-only users were not affected according to the report above.
If you interacted with v2.68, treat that environment as potentially exposed. A cautious approach is to rotate to a fresh wallet and monitor official notices before using the extension again.
2. Likely Mechanism
While the precise root cause is still being finalized, investigators pointed to insider risk as the most likely explanation for how a compromised build passed official checks (insight). Some coverage describes malicious JavaScript embedded in the extension update that exfiltrated sensitive data, including seed phrases, when accessed or imported (technical narrative).
Supply chain and release-pipeline controls matter as much as external exploit defenses. Until a detailed postmortem is published, avoid signing transactions via any extension that was updated during the affected window.
3. Impact and Response
Losses totaled around $7 million, and reimbursement for affected users was publicly pledged by Trust Wallets parent leadership and echoed by the team (confirmation). Investigators and community alerts flagged rapid drains, particularly when importing seed phrases into the extension during the compromised versions lifecycle (incident summary; broader coverage also appeared with user guidance in a news post).
Browser extensions have elevated permissions and are high-risk surfaces. Low depth and holiday timing can compound losses when compromise occurs, so vigilance on updates and permissions is a practical risk reducer.
Conclusion
The Trust Wallet compromise arose from a bad Chrome extension update that exposed seed recovery flows and enabled theft, with a patched version available and reimbursements pledged. The most important takeaway is operational security in the release pipeline, and until a full technical postmortem is out, treating recent extension sessions with caution is prudent.
CoinsKid.Com