0x32c57f5732c5…32c57f5a

ConfirmedSecurity528 vB51 sat/vB3 min decode

Aster Faces $4.56 Million API Wallet Transfer Allegations

A trader alleges seven transfers moved 4.56 million USDT through a browser-generated API key. Leonard says Aster tightened security and will help trace funds, but no reimbursement was announced.

Aster Says It Tightened Security After API Wallet Leak
WitnessAster Says It Tightened Security After API Wallet LeakSmithsonian Institution / Smithsonian · CC0

Outputs

  1. A trader alleged seven transfers moved 4.56 million USDT within 44 minutes on Nov. 12; The Defiant could not verify the amount or permissions.

  2. The reimbursement claim seeks 33 BTC and about 2.2 million USDT, plus fees, in original assets.

  3. The trader said Aster disabled transfers to other accounts by default within six hours; Leonard did not confirm the change.

  4. ASTER fell about 32% from its intraday spike on Nov. 15; Leonard attributed the move to liquidations he called “likely malicious.”

  5. Leonard’s Nov. 17 statement promised continued fund tracing and agency cooperation but announced no reimbursement.

Seven transfers moved 4.56 million USDT from an Aster account to a newly registered account within 44 minutes on Nov. 12, according to trader furongfei, who made the allegation in a Nov. 16 post under the X handle @fuhuahuai. The Defiant could not independently verify the reported amount or the permissions applied to the transfers.

In a Nov. 17 public statement, Leonard said Aster had tightened security following the API wallet leak. His statement did not confirm the trader’s narrower claim that Aster disabled transfers to other accounts by default within six hours of the incident.

What controls does Aster’s API wallet use?

Aster describes an API Wallet as a delegated signing credential used for trading. Its documentation separates permissions for spot trading, perpetual futures trading and withdrawals. It also says deleting an authorized agent revokes that agent’s ability to trade through the API. The scope therefore bears directly on the trader’s claim.

The trader said a browser-generated key called ‘aster-desktop’ signed the disputed transfers rather than the main wallet, and said the key carried no withdrawal permission. The trader therefore disputed whether Aster enforced the documented limits when processing the transfers.

Aster’s published transfer rules classify a transfer to another registered user as a withdrawal-level operation and require a signature from the source account’s wallet private key. Whether the platform applied that rule to the seven disputed payments remains unverified.

What happened during the 44-minute transfer window?

According to the Nov. 16 post, seven transfers moved 4.56 million USDT on Nov. 12, with the funds going to a newly registered account. The trader said 33 BTC had been sold and that the sale proceeds, along with existing USDT, had been transferred out.

Rather than wait for the funds to be recovered, the trader is seeking reimbursement in the original assets: 33 BTC and about 2.2 million USDT, plus fees.

Did the API wallet issue explain ASTER’s price move?

The API wallet disclosure is not a confirmed explanation for ASTER’s Nov. 15 price swing. The Defiant reported that day that the token fell about 32% from its intraday spike. Leonard attributed the volatility to liquidations of highly leveraged positions, calling them “likely malicious.”

Leonard’s Nov. 17 statement did not connect the market move with the transfer incident. The API wallet issue remains an unconfirmed explanation rather than a demonstrated cause.

What remains unresolved?

Aster’s security response does not settle the authorization dispute. The trader says the browser-generated key lacked withdrawal permission; Aster’s rules require a source-wallet private-key signature for registered-user transfers. The alleged amount and claimed permission mismatch remain unverified.

Leonard said Aster would keep helping trace the funds and cooperate with law enforcement and security agencies when needed. His statement did not announce reimbursement.

With no deadline or reimbursement commitment in Leonard’s statement, the immediate checkpoint is whether tracing and any law-enforcement work recover assets before the parties resolve the request. For similar incidents, practical enforcement of the private-key requirement will determine whether delegated API credentials remain constrained to their documented permissions.

via cryptonews.net (Source)

More from Daniel Okafor

Daniel Okafor

Show full bio

Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.

1,514 articles