
Aster has strengthened its platform security measures after confirming that a user suffered financial losses following the exposure of an API Wallet private key. The affected user, who goes by furongfei on X, reported losing approximately $4.56 million through unauthorized transactions, including the movement and subsequent sale of Bitcoin holdings. According to Lookonchain, the transactions occurred during the early hours of November 13 Beijing time, with the user maintaining they had not authorized any of the transfers. Seven transfers totaling 4,564,675.50 USDT were made to a newly registered account within 44 minutes, while 33 BTC were moved between the exchange's futures and spot markets nine times before being sold through 17 market orders.
ASTER has rebounded 4.29% to $0.5342 after experiencing a dramatic 32.5% price decline from $0.7124 to $0.4812 during November 16 trading, following a brief rally that saw the token surge nearly 30% within an hour. According to AMBCrypto, the token's daily chart shows bulls fighting to recover ground, with ASTER breaching the 23.6% Fibonacci level at $0.5236, suggesting buyers have successfully reclaimed part of the preceding decline. However, technical indicators present a mixed picture - while OBV's sharp rebound indicates buyers have returned to the market, RSI at 31.99 highlights that bullish momentum remains extremely weak despite recovering from deeply oversold territory. The H4 chart offers a more cautious outlook, with OBV starting to tick downward again after its initial rebound, indicating that buying interest is losing strength.
As reported by crypto.news, Leonard acknowledged the unusual trading activity and said the platform was working to establish what had happened. In his statement, he wrote, 'The price volatility is a result of liquidations of highly leveraged positions, likely malicious.' His explanation pointed to forced closures of leveraged positions, although the investigation has not yet established whether traders deliberately caused those liquidations or who may have been involved. The CEO sought to reassure users about the exchange's operations, stating 'Aster is running business as usual' and adding 'We do not have any such arrangement with any market makers.' According to BlockBeats, the team has emphasized that this price fluctuation is unrelated to the market-making arrangements for the ASTER token, with the team having not entered into any related cooperation agreements with market makers.
Liquidation data from Coinglass shows $9.09 million in ASTER positions closed over 24 hours, 2.71 times the seven-day average. The busiest hour for liquidations aligned precisely with the crash period, with long positions accounting for $5.95 million of the total and shorts $3.14 million. Binance carried the largest share at $3.75 million, while Aster's own platform followed with $2.97 million, split almost evenly between longs and shorts. As per BeInCrypto Markets, the token recovered gradually from the crash, reaching $0.54 at press time, up 3.9% over 24 hours. However, the token remains under significant pressure with weekly and monthly losses of 14.9% and 22.28% respectively, still trading more than 77% below its September 2025 record high of $2.41.
As part of its security response, Aster has pledged to help trace missing funds and cooperate with law enforcement agencies when needed. The affected user has requested compensation in the original assets, including 33 BTC, approximately 2.2 million USDT and forced liquidation fees, without having to wait for the recovery of the missing funds. Leonard instructed users who believe their API Wallet credentials may have been exposed to access the platform from a trusted device and immediately delete the compromised wallet. The CEO urged all users to keep their wallet private keys secure and be wary of phishing links and unknown browser extensions. According to Aster's official API documentation, users can configure permitted IP addresses and set expiration times for authorized agents, with account holders able to modify permissions or revoke authorization as needed.