CoinDCX said it will absorb the 15.99 million USDT loss from an old wallet attack and stressed that user funds are safe, while Tether has frozen addresses linked to the incident.
Event Progress: CoinDCX to Bear Losses from Old Wallet Attack
Based on the information provided, crypto exchange CoinDCX issued a follow-up statement on the old wallet attack, saying it will bear the 15.99 million USDT loss caused by the incident and emphasizing the safety of user funds. The incident involves an old wallet, erroneous user deposits and the trading platform's backstop arrangement, with the relevant losses borne by the platform rather than absorbed by users themselves. Reports on the same incident also show that Tether has frozen addresses related to the attack, providing cooperation for subsequent fund tracing and risk control.
Key Facts: Loss Scale and Liability Allocation Clarified
From the disclosed information, the core facts of the incident include three aspects: first, the target of the attack was an old wallet; second, the loss amount was 15.99 million USDT; third, CoinDCX explicitly stated that it will bear the losses and said user funds are safe. For a trading platform, old wallet management, handling of erroneous user deposits and determination of liability are directly involved in the incident. By choosing to have the company bear the losses, CoinDCX is in effect prioritizing stabilizing user expectations in its incident response and preventing users from suffering direct losses due to erroneous deposits or old wallet issues. Tether's freezing of related addresses means the stablecoin issuer provided cooperation in the incident response, which helps limit further movement of related funds, but the source material did not disclose the frozen amount, the number of addresses or subsequent recovery details.
Old Wallets and Erroneous User Deposits Become Risk Focus
The source material mentions that the incident involves old wallets and erroneous user deposits, indicating that the attack was related to old wallet management and user deposit paths. If old wallets remain connected to platform systems or user deposit addresses, the asset exposure surface may increase; erroneous user deposits may cause funds to enter unexpected addresses, increasing the difficulty of handling. CoinDCX bearing the losses and emphasizing user fund safety shows that the platform is attempting to isolate the impact of the incident from user assets. However, the source material did not further explain the specific methods for safeguarding user funds, the compensation process, the scope of affected users or follow-up arrangements for the old wallets. Therefore, what can currently be confirmed is that the company has made a public statement on bearing the losses, and Tether's freezing of related addresses forms part of the incident response.
Exchange Security Response Enters Liability-Bearing Phase
In crypto exchange security incidents, attack disclosure, loss confirmation, liability bearing and fund tracing are usually consecutive steps. Public information on the CoinDCX incident shows that the platform has moved from attack confirmation to loss bearing and is seeking to reduce fund transfer risks through cooperation with Tether in freezing related addresses. For users, whether the platform provides a backstop, whether user funds are safe and whether old wallets are disabled or migrated are key to measuring the quality of incident handling. For the industry, old wallet management, erroneous user deposit handling and cooperation with stablecoin issuers are becoming important components of exchange security response. The phrase company backstop in the source material also reflects that trading platforms need to assume more operational responsibility in security incidents rather than merely shifting risk to users.
Follow-up: Compensation Arrangements and Fund Tracing Progress
Directions requiring follow-up include: whether CoinDCX's assumption of the 15.99 million USDT loss is implemented through specific compensation or accounting treatment; whether risks related to the old wallet have been isolated; whether a clear handling mechanism has been formed for erroneous user deposits; whether fund tracing after Tether froze the addresses has made further progress; and whether the platform discloses more complete proof of user fund safety. The above information has not yet been expanded in the source material, and the incident remains at the stage of company statement and follow-up handling. For crypto exchanges, transparency in security incidents, liability bearing and user communication will directly affect the market's judgment of their risk management capabilities.
