0x5988d7715988…5988d774
Aster User Reports $4.56M Unauthorized Transfer as Token Swings 30%
An Aster user says $4.56M and 33 BTC moved via an Agent Key without a single signed transaction, as the platform probes both the breach and a 30% token swing.

Outputs
Aster user reported ~$4.56M in unauthorized transfers across seven transactions over ~44 minutes on Nov. 13
33 Bitcoin was moved between futures and spot accounts and sold via 17 market orders
The Aster token swung more than 30% overnight, falling to $0.4812
Transfers used an Agent Key labeled 'aster-desktop' despite a transfer-blocking privacy mode being on
Aster formed an investigation team; some funds reportedly flowed to Tornado Cash and NEAR Intents
A user of the decentralized perpetual futures platform Aster says roughly $4.56 million in assets was transferred and sold from the account without authorization, in a seven-transfer sequence that completed in about 44 minutes on Nov. 13. The disclosure, posted on X on Nov. 16 by an account identifying itself as Aster user "furongfei," alleged that the platform's permission controls failed during transfers executed through a trading credential Aster itself issues: an "Agent Key."
The user stated that the abnormal movements occurred in the early hours of Nov. 13. "I did not sign a single transaction, and I did not lose my wallet private key," the account wrote. Despite that, Aster approved seven transfers, the user said.
How the transfers unfolded
Records the user published show the transfers were executed with an Agent Key labeled "aster-desktop." The user described this credential as a temporary key generated in the browser after trading is enabled on Aster's website and approved through a wallet connection. In effect, it is a delegated permission that sits below the wallet signature layer.
According to the user's account of the on-chain and platform records:
- Someone used the Agent Key to register a new account on Aster.
- Over approximately 44 minutes, seven transfers moved roughly $4.56 million into that new account.
- In the same process, 33 Bitcoin held by the user moved between futures and spot accounts, then sold through 17 market orders.
- The transfers were approved even though a privacy mode intended to block internal transfers had been switched on.
- Some of the transferred funds later flowed to Tornado Cash and NEAR Intents, according to the user.
The user demanded repayment in the original assets.
What does this change for practitioners?
The allegation, if substantiated, turns on a specific operational question: whether a delegated Agent Key can move eight-figure-notional positions without a fresh wallet signature, and whether a transfer-blocking privacy mode is enforced server-side or merely advisory. For traders on delegated-key architectures, the working assumption until Aster's investigation concludes must be that enabling trading creates a standing permission whose compromise or misuse is not bounded by the underlying wallet's controls.
Ccweb3hub, an Aster account manager, replied that the company had formed an investigation team. The manager also urged users to protect their private keys and account access — guidance that does not, on its own, address the Agent Key mechanism at the center of the complaint, since the user maintains the wallet key was never exposed.
A separate price event, a linked question
Independently of the account breach claim, the Aster token swung more than 30% overnight and fell as low as $0.4812 during trading. Some market participants speculated the drop was tied to Aster's market-making activity. Aster said it is investigating whether abnormal price moves occurred during the liquidation of highly leveraged trading positions.
The two events may be unconnected. But a 30% overnight drawdown coinciding with an unresolved account-compromise claim compounds the operational scrutiny on the platform. Liquidations of highly leveraged positions can cascade mechanically when liquidity thins, and a platform that is simultaneously fielding questions about key permissions and market-making conduct now faces both inquiries in the same news cycle.
For the roughly $4.56 million at issue — and the 33 BTC sold through 17 market orders, a sum in the low millions of dollars at recent prices — the practical question is liability allocation. The user frames the failure as a platform permission-control defect; Aster has not publicly accepted or rejected that framing. No timeline for the investigation team's findings has been published, and the user's demand for repayment in original assets remains unanswered in public.
via en.bloomingbit.io (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