MEXC’s customer service team said on Sept. 28 that it had completed an initial review into a case involving abnormal transfers from a user account and had provided a corresponding solution. The exchange said it will continue handling the matter through one-on-one email communication, updating the user on progress and any required information, and advised users to watch their registered email inboxes and official channel messages.
The response followed a post on X by a MEXC user, who said the account was taken over after someone reset its security settings. According to the user, 322,110 USDT and 9,133,999 ONE were transferred out between 04:12 and 04:25 Beijing time on Sept. 27, for a combined value of about $340,000. The user added that the transfers took place roughly 27 minutes after a 24-hour withdrawal restriction was lifted.
The user said MEXC had confirmed the account was compromised and froze it to assist recovery, but had not revoked an API left by the attacker. The user also said a formal compensation claim had been submitted under ticket number M2026092712031.
According to ChainCatcher, MEXC’s customer service team said on Sept. 28 that it had completed an initial review into abnormal transfers from a user account and had provided a corresponding solution. The exchange said it will follow up with the user through one-on-one email communication, sharing handling progress and any information required, and reminded users to pay attention to messages sent to their registered email addresses and through official channels.
Earlier, a MEXC user wrote on X that the account was taken over after someone reset its security settings. The user said 322,110 USDT and 9,133,999 ONE were transferred out between 04:12 and 04:25 Beijing time on Sept. 27, with a combined value of about $340,000. The user added that the transfers occurred about 27 minutes after a 24-hour transfer restriction had been lifted.
The user also said MEXC had confirmed the account was compromised and froze the account to assist with recovery, but did not revoke an API left behind by the attacker. The user said a formal claim had been submitted under ticket number M2026092712031.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
