0x0d8a5b620d8a…0d8a5b65

ConfirmedSecurity546 vB58 sat/vB3 min decode

Aster Opens Investigation Into $4.56 Million Proxy-Key Transfer

Aster formed an investigation team after a user reported $4.56 million moved in seven transfers signed by a browser-generated proxy key the user says lacked withdrawal rights.

Aster Opens Probe After User Reports $4.56 Million Transfer
WitnessAster Opens Probe After User Reports $4.56 Million TransferShubham Dhage / unsplash

Outputs

  1. A user reported roughly $4.56 million moved in seven unauthorized transfers from an Aster account.

  2. Transfers occurred early Nov. 13 Beijing time (Nov. 12 ET), per the user's post on X.

  3. Aster's preliminary assessment found the browser-generated proxy key 'aster-desktop' was exposed.

  4. The user says the main wallet's private key was not compromised and no transaction was signed.

  5. Aster has formed an investigation team; no recovery or restitution process has been announced.

Aster has opened an investigation after a user reported that roughly $4.56 million was moved from their account in seven unauthorized transfers executed with a temporary proxy key generated in the platform's web interface.

The user, posting on X under the handle @fuhuahuai, said the transfers occurred in the early hours of Nov. 13 Beijing time, equivalent to Nov. 12 in the U.S. Eastern time zone. The user reported that an "agent key" created through Aster's web interface was used to establish a new account and carry out the transfers, with each transaction signed by that key. That figure — $4.56 million across seven movements — works out to an average of roughly $650,000 per transfer.

What does the user say happened?

The user's account rests on a specific technical claim: no transaction was personally signed, and the main wallet's private key was never exposed. The user stated that Aster's own documentation does not grant the proxy key withdrawal-level permissions. The account also had privacy mode enabled, a setting the user says was designed to block internal transfers.

Those two controls — documented permission limits and privacy mode — both appear to have failed to prevent the outbound movement of funds. Neither Aster nor the user has yet explained how a key with allegedly restricted permissions executed withdrawals of this scale.

How does Aster explain the incident?

Aster identified the credential involved as a temporary proxy key, designated "aster-desktop," generated locally in the browser following web authorization. The platform's preliminary assessment concluded that the proxy key itself had been exposed.

Aster draws a clear line between this browser-generated proxy key and the account's main wallet private key. That distinction matters: if the proxy key alone was compromised, the incident would point to flaws in the delegation mechanism rather than a full wallet compromise. The preliminary finding is, however, an early-stage attribution. Aster has not disclosed how the exposure occurred, whether other accounts generated similar keys, or what the on-chain trail of the seven transfers shows.

The platform has formed an investigation team and advised the user to secure the private key and account permissions. That advice is defensive; it does not address recovery of the $4.56 million, and no restitution pathway has been announced.

What remains unanswered?

Several operational questions are open. The mechanism by which a proxy key without documented withdrawal permissions executed transfers remains unexplained. Whether privacy mode was bypassed, misconfigured, or irrelevant to this attack path is also unclear. Aster has not said whether the investigation will be made public or whether other users' proxy keys are being audited as a precaution.

The incident also raises a broader design question for platforms that use browser-local key generation: a credential created client-side inherits the security posture of the browser environment, and Aster's preliminary exposure finding does not yet identify the point of failure. Until the investigation team publishes findings, the user's claim that no transaction was signed stands as an assertion, not a verified fact.

The immediate takeaway is simple: $4.56 million moved through a delegated key the user says lacked withdrawal rights, and Aster's own review is the only process currently testing that claim.

via tokenpost.com (Source)

More from Elena Vasquez

Elena Vasquez

Show full bio

Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.

1,525 articles