In This Article
Aster strengthens security after API wallet private key leak and a loss of $4.56 million.

Decentralized perpetual futures exchange Aster has strengthened its platform’s security measures after confirming that one of its users suffered financial losses as a result of an API wallet private key leak.

In a November 17 statement on X, Aster CEO Leonard Leung said the decentralized exchange began investigating the incident immediately after receiving a message from the affected user. The team examined the circumstances surrounding the loss of funds and conducted a review of the platform’s systems.

“Recently, an Aster user suffered losses as a result of the compromise of their API wallet’s private key. I regret this incident,” Leonard wrote in his statement.

The CEO’s response followed a complaint from an Aster user who reported losing approximately $4.56 million as a result of unauthorized transactions, including the movement and subsequent sale of bitcoin.

Aster user reports unauthorized transfers totaling $4.56 million

The affected user, registered on X under the handle furongfei, said the transactions took place in the early hours of November 13, Beijing time. The user claimed they did not authorize any of the transfers and that the private key of their primary wallet was not compromised.

An investigation conducted by Lookonchain found that someone used an agent key generated automatically via Aster’s web interface to register a new account.

According to the user’s description of the transactions, seven transfers totaling 4,564,675.50 USDT were made to a newly registered account within 44 minutes. Over the same period, 33 BTC were moved between the exchange’s futures and spot markets nine times, and were then sold via 17 market orders.

The user claimed that none of the seven transactions contained a signature from their primary wallet. Instead, the transactions were signed using a temporary private key labeled “aster-desktop,” which was generated locally in the browser when the user enabled trading and completed the wallet authorization.

After the user contacted the platform regarding the missing funds, Aster initially formed an investigative team.

Aster API wallet permissions undergo thorough review

Part of the user’s complaint concerns the permissions assigned to the compromised trading credentials. The user claimed the agent key did not have withdrawal permission and that the account’s privacy settings prohibited internal transfers to other users.

Aster’s official API documentation describes separate permissions for spot trading, perpetual futures trading, and withdrawals. Users can authorize an agent wallet to perform certain operations on their behalf without using their primary wallet’s private key to sign every trading request.

The documentation provides options for configuring allowed IP addresses and setting an expiration time for the authorized agent. Subsequently, account owners can change permissions or revoke an agent’s authorization.

Aster CEO pledges to assist in recovering the funds

Meanwhile, the affected user stated that approximately 4.56 million USDT was subsequently withdrawn from the newly registered account in 10 transactions.

According to available information, part of the funds was transferred between blockchain networks: 1,000 ETH went to the cryptocurrency mixing protocol Tornado Cash. Another 768.1 ETH and approximately 994,000 USDT were reportedly transferred via NEAR Intents.

Leonard stated that Aster would continue to participate in efforts to locate the missing assets.

“We will continue to help users track the movement of funds and cooperate with law enforcement and security services where necessary,” the CEO wrote.

The affected user demanded compensation in the form of the original assets, including the 33 BTC, approximately 2.2 million USDT, and forced liquidation fees, without having to wait for the missing funds to be recovered.

The compensation request calls for the preservation of the platform’s server logs and the provision of a written timeline for reviewing the case. In his latest statement, Leonard did not announce a decision regarding reimbursement.