Exchanges split NES holders after $286M exploit

A token-contract security incident on Aug. 24 led to differing recovery rules from two major exchanges, leaving some NES token holders eligible for 1:1 swaps and others routed to refunds or left unable to move tokens on certain chains. The exploit affected Nesa’s NES token and has prompted exchange-specific responses rather than a single, network-wide recovery plan.

Binance Alpha applied two time-based snapshots to determine swap and refund eligibility. To receive a 1:1 swap for a portion of NES on Binance Alpha, an account had to hold NES before Aug. 24 at 14:51 UTC and still hold an eligible portion when trading was suspended on Sept. 5 at 04:00 UTC. NES purchased after the Aug. 24 cutoff is excluded from the 1:1 swap and will be handled through a refund process. Trading on Binance Alpha reopened at 08:00 UTC on Sept. 10. Binance Alpha said account holders with eligible net purchases during the snapshot window will get an email with refund details within seven business days and did not publish a full refund formula or a guarantee of full compensation for all affected holders.

Kraken restored Ethereum deposits and withdrawals for NES on Sept. 10 at 14:00 UTC and resolved its funding incident minutes later. Kraken plans to migrate NES covered by its funding incident 1:1 to a new Ethereum contract and will continue to disable NES funding on the BNB Chain. Customers moving NES to or from Kraken are directed to select Ethereum and to verify the new contract details provided in Kraken’s official notice before transferring funds.

Neither exchange notice provides a universal migration path for NES tokens held in private wallets. Nesa’s public site and its general wallet documentation did not include incident-specific self-custody migration instructions at the time of the exchanges’ announcements. Holders who control private keys should verify any contract address and migration process directly through Nesa’s official channels before approving a contract interaction or transferring tokens from the old contract.

The differing rules create distinct outcomes depending on where and when tokens were held. Account holders on both platforms are advised to check which snapshot category applies to their balances, monitor communications sent to the email address tied to their exchange account, and confirm contract details before initiating transfers.