0x74f2f62474f2…74f2f627
Aster hardens security after API Wallet key leak drains $4.56M
Aster CEO Leonard Leung confirmed a $4.56M loss from a leaked API Wallet key, as the user demands compensation in 33 BTC and 2.2M USDT amid scrutiny of agent-key permissions.

Outputs
An Aster user lost approximately $4.56 million (4,564,675.50 USDT) via seven unauthorized transfers within 44 minutes on Nov. 13.
CEO Leonard Leung confirmed the API Wallet private key compromise in a Nov. 17 statement on X.
Stolen funds included 33 BTC sold via 17 market orders; 1,000 ETH was routed through Tornado Cash.
The user demands compensation in 33 BTC and about 2.2 million USDT without waiting for fund recovery.
Aster's native token fell from $0.7124 to $0.4812 on Nov. 16 in a separate leveraged-liquidation event.
Decentralized perpetual futures exchange Aster has confirmed that a user lost approximately $4.56 million after an API Wallet private key was compromised, and has pledged to help trace the missing funds and cooperate with law enforcement. CEO Leonard Leung disclosed the incident and the platform's security response in a Nov. 17 statement on X, days after the affected trader publicized the loss.
The victim, who posts on X under the handle furongfei, reported that roughly 4,564,675.50 USDT left their account through seven unauthorized transfers executed within 44 minutes during the early hours of Nov. 13 Beijing time. The user maintains that none of the transfers carried a signature from their main wallet and that their main private key was never compromised.
"Recently, an Aster user suffered asset losses after their API Wallet private key was compromised. I regret this incident," Leung wrote.
How did the attacker move the funds?
According to details relayed by on-chain analytics firm Lookonchain, the attacker used an agent key automatically generated through Aster's web interface to register a new account. The seven USDT transfers landed in that newly registered account inside the 44-minute window.
In parallel, the attacker moved 33 BTC between Aster's futures and spot markets nine times before selling the holdings through 17 market orders. The user stated the transactions were signed with a temporary private key labeled "aster-desktop," generated locally in the browser when the user enabled trading and completed wallet authorization.
The trail did not end on the exchange. The affected user said the receiving account subsequently withdrew approximately 4.56 million USDT across 10 transactions. Of that amount, 1,000 ETH entered the Tornado Cash mixing protocol, while another 768.1 ETH and roughly 994,000 USDT were routed through NEAR Intents, according to the user's account of the on-chain flows.
What does this change for API Wallet users?
The complaint puts Aster's agent-key permission model under scrutiny. The user alleged the compromised credential did not have withdrawal authorization and that the account's privacy settings prohibited internal transfers to other users — restrictions that, on the user's reading, should have blocked the seven-transfers-to-a-new-account sequence at the center of the incident.
Aster's official API documentation describes separate permissions for spot trading, perpetual futures trading and withdrawals. Users can authorize an agent wallet to perform designated operations without signing every trading request with their main wallet private key. The documentation allows configuring permitted IP addresses and setting expiration times for an authorized agent, and account holders can modify permissions or revoke authorization at any time.
Leung did not address the permission discrepancy directly. "We will continue to help users trace the flow of funds and cooperate with law enforcement and security agencies when needed," he wrote.
Crypto.news reached out to Aster for comment on the reported losses, the API Wallet permissions and potential compensation, but had not received a response by press time.
What is the user demanding?
The affected trader has requested compensation in the original assets — 33 BTC and approximately 2.2 million USDT, plus forced liquidation fees — without waiting for recovery of the missing funds. The request also calls for preserving the platform's server logs and providing a written timeline for handling the case. Leung announced no reimbursement decision in his statement.
The incident is the second operational event to hit Aster in under a week. On Nov. 16, the platform's native token fell from $0.7124 to $0.4812 within minutes. Leung attributed that episode to liquidations of highly leveraged positions and described the activity as "likely malicious."
What should traders do now?
As part of its security response, Aster urged users to safeguard private keys and to treat unfamiliar links and browser extensions with caution. "We also remind all users to keep their wallet private keys secure and be wary of phishing links and unknown browser extensions," Leung said.
Users who suspect their API Wallet credentials have been exposed should access the platform from a trusted device, navigate to the API Wallet management page and delete the compromised wallet immediately. Per Aster's documentation, deleting an authorized agent revokes its ability to conduct API trading.
The open questions now rest with Aster's investigation and any law enforcement follow-through: whether the agent-key permission set failed as the user alleges, and whether the exchange will treat the loss as a platform liability or an isolated client-side compromise.
via crypto.news (Source)
More from Nathan Brooks
Show full bio
Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,512 articles