TLDR
Trust Wallet says it has identified 2,596 affected addresses tied to its recent browser?extension incident, now in a verification phase to filter false claims per a media report.
- Losses are about $7 million, with full refunds pledged to verified victims per an update.
- Impact is limited to Browser Extension v2.68%%CKPROTECTED2%%; mobile and other versions were not affected per a report.
- Nearly 5,000 claims were submitted, suggesting many are duplicates or false, per the report above.
Deep Dive
1. Address Count
Trust Wallets team moved from triage to verification and reported 2,596 affected addresses after its Christmas Day exploit in the browser extension. The verification step is meant to ensure only legitimate victims are reimbursed per the report.
If you think youre affected, expect stricter ownership checks before reimbursement, and rely on official channels referenced in the notice above.
2. Loss Magnitude and Refunds
The company stated approximately $7 million was impacted and committed to fully refund verified victims, aligning with public statements that user funds would be covered per an update.
- Investigators and media estimated losses in the $67 million range during the first 48 hours, with funds moved across several venues per a market update.
- Trust Wallet emphasized accuracy over speed to avoid reimbursing false claimants per the report above.
Refunds are likely, but timing depends on verification. Keep evidence organized (addresses, hashes) for the review process mentioned in the notice above.
3. Scope and Next Steps
The incident impacted Browser Extension version 2.68%%CKPROTECTED2%% only; mobile users and other versions were not affected, and users were urged to update to v2.69 per a report.
- Reports cited multiple chains (BTC, ETH, SOL) among affected wallets per a roundup.
- The company is conducting forensic work to finalize data and prevent process abuse, per the report above.
If you previously used v2.68, confirm your version and monitor the official communications in the notice above; avoid importing seed phrases into browser extensions until guidance is clear.
Conclusion
The best current figure is 2,596 affected addresses, with about $7 million in losses and refunds promised to verified victims. The impact was confined to the extensions v2.68%%CKPROTECTED5%%, and the verification process explains the gap between identified addresses and higher claim counts. For users, verification rigor and version hygiene are the immediate levers that reduce risk and speed remediation.
CoinsKid.Com