Aster, the decentralized perpetual futures exchange, confirmed that a user suffered losses of roughly $4.56 million after the private key of an API wallet was compromised, according to a statement posted by CEO Leonard Leung on X on November 17.

BTC / USD
Source: CoinGecko. Prices are indicative.

Details of the breach

The affected account, identified on X as “furongfei,” said the breach occurred in the early hours of November 13 Beijing time. Seven unauthorized transfers totalling 4,564,675.50 USDT were sent to a newly created account within a 44‑minute window, and 33 BTC were moved between Aster’s futures and spot markets nine times before being sold via 17 market orders. The transactions were signed with a temporary private key generated locally in the browser, labelled “aster‑desktop,” rather than the user’s main wallet key.

Aster’s response and security measures

Aster immediately launched an investigation, examined platform logs and began cooperating with law‑enforcement agencies. The exchange urged all users to delete any compromised API wallets from trusted devices and to review API permissions, which can be limited to trading without withdrawal rights. Leung emphasized the need to protect private keys, avoid phishing links and unknown browser extensions, and to revoke any suspect agent keys via the API wallet management page.

Fund recovery and compensation request

The user claimed that the stolen assets were partially moved through mixing services, including 1,000 ETH sent to Tornado Cash and 768.1 ETH plus about 994,000 USDT routed via NEAR Intents. The complainant is seeking compensation in the original assets—33 BTC, roughly 2.2 million USDT and forced‑liquidation fees—while preserving server logs and a timeline of the incident. Aster has not announced a reimbursement decision but said it will continue to assist in tracing the funds.

What to watch next

Observers will monitor whether law‑enforcement agencies can recover any of the missing crypto, how Aster’s tightened API‑wallet controls affect future security incidents, and whether additional users experience similar breaches as the platform refines its permission model.