Aster has tightened its security procedures after confirming that a user suffered financial losses following the exposure of an API Wallet private key.
The decentralized perpetual futures exchange said it began investigating the incident after receiving a report from the affected user, who claims approximately $4.56 million in cryptocurrency was moved through unauthorized transactions.
Aster CEO Leonard Leung said the company is reviewing the circumstances surrounding the loss, helping trace the funds and cooperating with law enforcement and security agencies where necessary.
The incident has also renewed scrutiny around the permissions granted to Aster’s API Wallet system and the risks associated with browser-generated trading credentials.
Aster confirms API Wallet private key compromise
Leung said on November 17 that an Aster user had suffered asset losses after an API Wallet private key was compromised.
He said the company began investigating the case immediately after being notified.
Aster also carried out checks on its platform systems as part of the response.
The CEO described the incident as regrettable but did not announce a final reimbursement decision.
User reports approximately $4.56 million in losses
The affected user, known as furongfei on X, said the unauthorized activity occurred during the early hours of November 13 Beijing time.
The user maintained that none of the transactions had been approved and that the private key controlling the main wallet had not been compromised.
According to details later reported by Lookonchain, the disputed transfers totaled approximately 4.56 million USDT.
Seven transfers reportedly occurred within 44 minutes
The user said seven transfers totaling 4,564,675.50 USDT were made to a newly registered account over a period of 44 minutes.
The complaint also described substantial activity involving Bitcoin.
During the same period, 33 BTC were reportedly moved nine times between Aster’s futures and spot markets before being sold through 17 market orders.
The sequence raises questions about how much authority the compromised credential had over the account.
Main wallet allegedly did not sign the transfers
The user said none of the seven disputed transfers carried a signature from the main wallet.
Instead, they were reportedly signed using a temporary private key identified as “aster-desktop.”
According to the user, this credential had been generated locally inside the browser when trading was enabled and wallet authorization was completed.
That distinction is central to the dispute.
What is an Aster API Wallet?
Aster’s API system allows users to authorize an agent wallet to perform selected operations on their behalf.
This means users do not need to sign every trading request manually with their primary wallet.
The arrangement can improve convenience for active traders and automated systems.
However, it creates another credential that must be protected.
Agent keys can create a separate attack surface
A primary wallet may remain secure while an API or agent key is compromised.
If that secondary credential has broad permissions, an attacker may still be able to place trades or perform other account actions.
The security of the overall account therefore depends not only on the main wallet but also on every authorized agent.
Aster’s documentation describes separate permissions
Aster’s API documentation identifies different permissions for functions such as:
- Spot trading
- Perpetual futures trading
- Withdrawals
Users can configure an agent wallet to perform designated actions.
The system also supports additional controls such as permitted IP addresses and expiration times.
Account holders can later change or revoke those permissions.
User disputes the level of authority available to the compromised key
Part of the complaint focuses on whether the exposed agent wallet should have been capable of performing the disputed transfers.
The user alleged that the credential did not have withdrawal authorization.
The user also said account privacy settings were configured to prevent internal transfers to other users.
Those claims have not yet been fully resolved publicly.
Permission design is now under scrutiny
The incident raises an important question for API-based trading systems.
A credential designed mainly for automated trading should not necessarily have unrestricted ability to move funds.
If trading, transfers and withdrawals use different permission levels, the exact scope of each credential becomes critical.
Users need to know what an API key can and cannot do after it is created.
The affected account allegedly registered a new user
According to the reported transaction history, an attacker used an agent key automatically generated through Aster’s web interface to register a new account.
The disputed assets were then reportedly transferred to that account.
This suggests the attacker may have used permissions beyond ordinary market-order execution.
The exact mechanism has not yet been independently established by the platform.
Aster formed an investigation team
After being contacted by the user, Aster created a team to investigate the missing funds.
The company has not publicly released a complete technical timeline of the incident.
It also has not published a detailed explanation of how the compromised API Wallet key was obtained.
That leaves phishing, browser compromise, malicious extensions and other attack paths under consideration.
Browser-generated credentials create additional security dependencies
If a trading key is generated locally in a browser, the security of that credential depends partly on the local environment.
Potential risks can include:
- Malicious browser extensions
- Phishing websites
- Compromised devices
- Clipboard malware
- Stolen local storage
- Session hijacking
Even a secure exchange backend cannot fully protect a key already stolen from the user’s device.
Browser extensions deserve particular attention
Leung specifically warned users about unfamiliar browser extensions.
Extensions can request powerful permissions.
A malicious extension may be able to observe page content, intercept credentials or manipulate interactions.
Crypto users should therefore be especially cautious about installing extensions from unknown sources.
Phishing remains another likely threat category
A phishing site can imitate a legitimate trading interface and trick users into approving or exposing sensitive credentials.
The user may believe they are authorizing a normal wallet action while actually granting access to an attacker.
That is why Aster urged users to navigate to trusted pages directly rather than follow unfamiliar links.
Funds were reportedly withdrawn in multiple transactions
The affected user said the newly created account later withdrew approximately 4.56 million USDT across 10 transactions.
Some of the funds were reportedly moved across different blockchain networks.
That can make recovery significantly more difficult.
Once funds leave the exchange, investigators must trace activity across several protocols and chains.
Tornado Cash reportedly received 1,000 ETH
The reported fund flows included approximately 1,000 ETH entering Tornado Cash.
Mixing protocols can make blockchain tracing more difficult by breaking the direct relationship between deposit and withdrawal addresses.
That does not make tracing impossible in every case.
But it can reduce investigators’ ability to follow funds using simple transaction history.
Additional funds reportedly moved through NEAR Intents
Another 768.1 ETH and roughly 994,000 USDT were reportedly routed through NEAR Intents.
Cross-chain systems can add complexity to tracing because assets can move through multiple networks and settlement mechanisms.
Security teams need to follow the complete path rather than examining only one chain.
Aster says it will help trace the assets
Leung said the platform would continue helping users trace the missing funds.
He also said Aster would cooperate with law enforcement and security agencies if required.
This is a common part of exchange incident response because centralized services may be able to freeze funds if stolen assets reach known accounts.
Recovery depends heavily on where the funds move
Crypto theft does not always mean assets are permanently unrecoverable.
Recovery may be possible if stolen funds:
- Reach a centralized exchange
- Interact with a compliant service provider
- Are frozen by law enforcement
- Remain identifiable on-chain
The chance of recovery usually decreases as funds are mixed, swapped or moved through many services.
The user has requested compensation
The affected user has asked Aster to compensate the losses using the original assets.
The request reportedly includes:
- 33 BTC
- Approximately 2.2 million USDT
- Forced liquidation fees
The user also wants compensation without waiting for the stolen funds to be recovered.
Aster has not publicly agreed to that request.
The user also wants server logs preserved
The compensation request includes preservation of Aster’s server logs.
That could be important for determining:
- Which credentials were used
- Which devices connected
- What IP addresses were involved
- What permissions were active
- How transactions were authorized
Detailed logs can help distinguish a platform-level vulnerability from a compromised user credential.
A written incident timeline has also been requested
The user has asked Aster for a formal timeline explaining how the company handled the case.
A clear incident report could help establish:
- When the first unauthorized action occurred
- When Aster detected or was notified of the issue
- When withdrawals occurred
- What defensive actions were taken
Transparency around these events will matter for rebuilding confidence.
Aster has not announced a reimbursement decision
Leung’s statement focused on investigation, security and fund tracing.
It did not confirm that Aster would reimburse the user.
That means the financial responsibility for the loss remains unresolved.
The eventual decision may depend on whether investigators determine that the compromise originated on the user side or from a flaw in Aster’s systems.
Platform liability and user credential compromise are different issues
If an attacker steals a user-controlled API key through phishing or malware, the platform may argue that its core system was not breached.
If a platform permission flaw allows an agent to perform actions outside its intended scope, responsibility looks different.
The exact technical findings therefore matter more than the headline amount lost.
Aster urges users to delete compromised API Wallets
As part of its response, Aster told users who suspect API Wallet exposure to access the platform from a trusted device.
They should then go directly to API Wallet management and delete the compromised credential.
Aster’s documentation says deleting an authorized agent revokes its ability to continue API trading.
Revocation should happen immediately after suspected compromise
Once an API key is suspected of being exposed, users should assume the attacker may still have it.
Changing unrelated account settings does not necessarily invalidate the key.
Revocation or deletion is therefore one of the most important first steps.
A trusted device matters during recovery
Users should not attempt to revoke a compromised key from the same device if they suspect that device is infected.
A malicious extension or local malware could potentially capture newly generated credentials or account changes.
Using a clean and trusted device reduces that risk.
Users should review all authorized API Wallets
The incident is also a reminder to periodically review active agent wallets.
Users may have old credentials they no longer need.
Unused API keys increase the attack surface.
A strong security routine should remove credentials that are no longer actively required.
Expiration times can reduce long-term exposure
Aster supports expiration settings for authorized agents.
Shorter-lived credentials can limit how long a stolen key remains useful.
They do not prevent the initial compromise.
But they can reduce the damage window if the key is exposed and the breach is not immediately detected.
IP restrictions can add another layer
Users can also configure allowed IP addresses for API credentials.
If implemented correctly, an attacker holding the key may still be unable to use it from an unauthorized location.
This is not perfect protection because IP addresses can sometimes be compromised or spoofed indirectly.
But it creates another barrier.
Principle of least privilege is critical
API Wallets should ideally receive only the permissions required for their specific task.
For example, a trading bot may need order-placement access.
It may not need withdrawal or transfer permissions.
Limiting authority reduces the damage possible if a credential is stolen.
Withdrawal permissions deserve especially strict controls
A credential capable of moving funds presents much higher risk than one limited to trading.
Platforms can reduce exposure through:
- Separate withdrawal keys
- Address allowlists
- Delayed withdrawals
- Strong secondary authentication
- Manual approvals
The exact controls vary by platform.
Trading permissions alone can still cause large losses
Even without direct withdrawals, an attacker with trading authority can potentially cause serious damage.
They may:
- Open highly leveraged positions
- Manipulate thin markets
- Trigger liquidations
- Sell assets at unfavorable prices
API security therefore matters even when withdrawal permission is disabled.
Aster was already investigating unusual market activity
The incident follows another recent security-related concern around Aster.
On November 16, the platform investigated unusual movements in its native ASTER token.
The token reportedly dropped from around $0.7124 to $0.4812 within minutes.
Leung attributed that episode to liquidations involving highly leveraged positions and described the behavior as likely malicious.
The two incidents should not automatically be treated as the same event
The API Wallet case involves an allegedly compromised user credential and unauthorized transfers.
The ASTER price event involved unusual liquidation activity.
There is no established evidence in the supplied report that both incidents originated from the same attacker or vulnerability.
They should be analyzed separately unless investigators establish a connection.
Multiple security incidents can still affect confidence
Even unrelated incidents occurring close together can damage user confidence.
Traders may begin questioning:
- Platform controls
- API permissions
- Liquidation systems
- Monitoring
- Incident response
Clear technical explanations become especially important in that environment.
Private key security remains the first line of defense
Leung reminded users to protect wallet and API private keys.
A private key or API credential can effectively authorize actions on behalf of the user.
Once exposed, the attacker may not need to compromise the underlying blockchain.
Security therefore needs to focus heavily on credential protection.
Never share API Wallet private keys
A legitimate support agent should not need a user’s API Wallet private key.
The same applies to recovery phrases and primary-wallet keys.
Requests for those credentials should be treated as a serious warning sign.
Users should verify domains before authorizing wallets
Crypto phishing sites often use domains that closely resemble legitimate platforms.
Users should navigate directly to known official websites and verify the domain before approving wallet requests.
Bookmarks can help reduce the risk of clicking fake search advertisements or phishing links.
Hardware wallets do not automatically protect API credentials
A hardware wallet can protect the primary signing key.
But an API Wallet credential generated separately in a browser may not receive the same protection.
That creates an important distinction.
Securing the main wallet does not automatically secure every delegated trading key.
API systems trade convenience for additional security responsibility
Agent wallets are useful because they enable automation.
A trading bot can operate without requiring a hardware-wallet signature for every order.
But that convenience means users must protect a secondary credential capable of acting on their behalf.
The more authority delegated, the more valuable that key becomes to attackers.
Platforms also need strong monitoring
User-side security is only one part of the defense.
Trading platforms can monitor for unusual activity such as:
- Large transfers to newly created accounts
- Sudden changes in trading behavior
- New device locations
- Rapid asset conversions
- Unusual API activity
Automated risk controls may help identify compromised accounts before all funds leave.
The 44-minute window raises monitoring questions
According to the complaint, seven disputed transfers occurred within 44 minutes.
That raises questions about whether unusual activity could have been flagged earlier.
However, without seeing Aster’s monitoring rules and normal account behavior, it is not possible to determine whether the activity should have triggered an automatic block.
Internal transfers may require additional safeguards
Transfers between accounts on the same platform can happen quickly because they may not require an external blockchain transaction.
That convenience can also be exploited if an attacker obtains sufficient account permissions.
Platforms may need additional controls for high-value internal transfers initiated through API credentials.
What users should do after suspected API key exposure
The immediate response should focus on stopping further access.
Use a trusted device:
Avoid a system that may contain malware.
Revoke the API credential:
Delete or disable the exposed agent wallet immediately.
Review recent activity:
Check transfers, orders and account changes.
Secure the main wallet:
Verify whether the primary private key remains safe.
Change relevant passwords:
Especially if phishing or device compromise is possible.
Preserve evidence:
Keep transaction IDs, timestamps and screenshots without exposing private credentials.
On-chain evidence should be preserved
Blockchain transactions provide a permanent public record.
Victims can preserve:
- Transaction hashes
- Destination addresses
- Token movements
- Cross-chain routes
That information can be useful for security firms, exchanges and law enforcement.
Device evidence can matter just as much
If malware or an extension is suspected, users should avoid immediately wiping the affected device without considering forensic needs.
Security specialists may be able to determine how the credential was stolen.
At the same time, the device should not continue to be used for sensitive crypto activity.
What Aster needs to clarify
Several questions remain unanswered.
Permission scope:
Could the compromised agent legitimately perform the disputed transfers?
Key exposure:
How did the “aster-desktop” credential leave the user’s browser?
Internal controls:
Were the seven transfers consistent with the permissions assigned?
Monitoring:
Did any anomaly detection trigger during the 44-minute period?
Compensation:
Will Aster reimburse any portion of the reported loss?
What to watch next
Technical incident report:
A detailed explanation would clarify whether the root cause was user compromise, API design or both.
Fund recovery:
Movement through exchanges or identifiable protocols could create opportunities for freezing assets.
Compensation decision:
Aster’s handling of the user’s reimbursement request will be closely watched.
Permission changes:
The platform may tighten API Wallet permissions after the investigation.
Security controls:
Additional IP restrictions, withdrawal safeguards or monitoring could follow.
Final thoughts
Aster’s reported $4.56 million API Wallet incident highlights a security problem that extends well beyond one exchange.
Crypto users increasingly rely on delegated credentials to automate trading.
Those API and agent keys can make platforms easier to use, but they also create additional secrets that attackers can target.
In this case, the affected user says the main wallet private key remained secure while a locally generated “aster-desktop” credential was used to authorize the disputed activity.
That makes the exact scope of the API Wallet’s permissions central to the investigation.
Aster says it is helping trace the funds and cooperating with authorities while advising users to revoke any potentially exposed API Wallets immediately.
The next major question is whether the incident resulted solely from the theft of a user-controlled credential or whether the compromised agent was able to perform actions beyond the permissions it was supposed to have.
That distinction will determine whether this was primarily an account-security failure, a platform-permission issue, or a combination of both.
Disclosure: This article is for informational and educational purposes only and does not constitute investment advice.


















































