Which Trust Wallet versions were hacked?

TLDR

Trust Wallet Browser Extension version 2.68 was the compromised build; mobile apps and other extension versions were not affected, and a patched 2.69 was released promptly (Trust Wallet update).

1. Affected: Chrome extension v2.68 only (incident confirmation).
2. Safe: Mobile app and other extension versions remained secure (official guidance cited).
3. Fix: Update to v2.69, and avoid opening v2.68 during investigation (patched release noted).

Deep Dive

1. Affected Build

The issue was limited to the Trust Wallet Chrome browser extension version 2.68, with reports of immediate fund drains after seed phrase imports and losses exceeding $6 million (extension 2.68 impact). Multiple outlets and community investigators corroborated that the breach coincided with the Dec 24 update cycle (incident details).

2. Safe Versions

Trust Wallet stated that mobile-only users and other extension versions were not impacted. The vulnerability was confined to the single extension release and did not reflect a protocol or chain-level failure (version scope and safety). Coverage emphasizes the risk profile of browser-based wallets rather than core blockchain security (context overview).

3. Patch and Guidance

A patched extension version 2.69 was released, and users were advised not to open the compromised 2.68 during remediation. Public statements also indicated reimbursement for affected users as part of ongoing response efforts (patched release and guidance). Outlets repeated instructions to disable v2.68 and upgrade to 2.69 immediately while investigations continue (update and scope).

Conclusion

Only Trust Wallets Chrome browser extension version 2.68 was compromised, with a fixed 2.69 issued quickly and mobile apps unaffected. The incident highlights browser-extension risk and the importance of strict key hygiene and version verification when handling seed phrases.