Trust Wallet Reveals Number of Victims from the Hack and the Compensation Problem

RBK-cryptoPublicado em 2025-12-29Última atualização em 2025-12-29

Resumo

Trust Wallet CEO Eowyn Chen revealed that last week's hack affected over 2,500 user accounts. However, the service has received approximately 5,000 compensation claims, indicating a significant number of fraudulent or duplicate requests, which is slowing down the payout process. The hack occurred on the night of December 26 due to a vulnerability in the browser extension version 2.68. An update (v2.69) was released, and the company promised to cover the estimated $7 million in losses. The verification of claims is being conducted alongside the technical investigation, prioritizing accuracy over speed. Trust Wallet is working with Google to obtain Chrome audit logs and is conducting a detailed security check on remote devices. In a related context, a recent Chainalysis report noted that 2025 has seen over 158,000 personal wallet compromises, resulting in $713 million in losses.

Trust Wallet head Eowyn Chen reported that last week's crypto wallet hack affected over 2,500 accounts. However, she stated that the service received twice as many compensation claims, which is slowing down payouts as it takes time to weed out fraudulent requests.

The Trust Wallet hack occurred on the night of December 26. Developers had previously acknowledged a vulnerability in the browser wallet version 2.68, released an update to version 2.69, and promised to compensate for the damage, which they estimated at $7 million.

"To date, we have identified 2,596 addresses affected by the hack. From this group, we have received about 5,000 claims, indicating a significant number of false or duplicate attempts to access victim compensation," wrote Chen.

The verification of claims is being conducted in parallel with the technical investigation of the incident. Chen noted that this has proven to be a complex task, so processing the requests is taking longer than affected users expected. The priority remains the accurate verification of wallet owners, not speed.

The day before, Chen reported that Google is assisting in the investigation—the crypto wallet team hopes to obtain audit logs (access request logs) from the Chrome browser. Also, the Trust Wallet security service will conduct a detailed check of the devices of employees working remotely.

A week earlier, Chainalysis estimated that the total damage from hackers' actions in 2025 exceeded $3.4 billion. This year, 158,000 cases of personal wallet compromises were recorded with a total damage of $713 million (compared to $1.5 billion the previous year), affecting over 80,000 users.

Bitcoin's price updated its weekly high. What happened to cryptocurrencies

Memecoin market cap plunged by $100 billion in 2025. CoinGecko report

"Overcoming the psychological barrier." What will happen to Bitcoin this week

Perguntas relacionadas

QHow many user accounts were affected by the Trust Wallet hack according to CEO Eowyn Chen?

AOver 2,500 accounts were affected by the Trust Wallet hack.

QWhat was the estimated financial damage from the Trust Wallet security breach?

AThe estimated financial damage from the hack was $7 million.

QWhy is the compensation process taking longer than expected for Trust Wallet users?

AThe process is taking longer because the service received about 5,000 claims for 2,596 affected addresses, indicating a significant number of fraudulent or duplicate claims that require time to filter out.

QWhich specific version of the Trust Wallet browser extension contained the vulnerability that was exploited?

AThe vulnerability was in the browser wallet version 2.68.

QWhat is the total estimated damage from hacker activities in 2025, as reported by Chainalysis?

AAccording to Chainalysis, the cumulative damage from hacker activities in 2025 exceeded $3.4 billion.

Leituras Relacionadas

From Theft to Re-entry: How Was $292 Million "Laundered"?

A sophisticated crypto laundering operation was executed following the $292 million hack of Kelp DAO on April 18. The attack, attributed to the North Korean Lazarus group, began with anonymous infrastructure preparation using Tornado Cash to fund wallets untraceably. The hacker exploited a vulnerability in Kelp’s cross-chain bridge, stealing 116,500 rsETH. To avoid crashing the market, the attacker used Aave and Compound as laundering tools—depositing the stolen rsETH as collateral to borrow $190 million in clean, liquid ETH. This move triggered a bank run on Aave, causing an $8 billion drop in TVL. After consolidating funds, the attacker fragmented them across hundreds of wallets to evade detection. A major breakpoint was THORChain, where over $460 million in volume—30 times its usual activity—was processed in 24 hours, converting ETH into Bitcoin. This shift to Bitcoin’s UTXO model exponentially increased tracing complexity by shattering funds into countless untraceable fragments. The final destination was Tron-based USDT, the primary channel for illicit crypto flows. From there, funds were cashed out via OTC brokers in China and Southeast Asia, using unlicensed underground banks and UnionPay networks outside Western sanctions scope. Ultimately, the laundered money supports North Korea’s weapons programs, which rely heavily on crypto hacking for foreign currency. The incident underscores structural challenges in DeFi: its openness, composability, and lack of central control make such laundering not just possible, but inherently difficult to prevent.

marsbitHá 3h

From Theft to Re-entry: How Was $292 Million "Laundered"?

marsbitHá 3h

Trading

Spot
Futuros
活动图片