ACryptoS Exploit on Base: How to Withdraw From Affected Vaults
An input-validation bug let an attacker drain about $665,000 from 77 ACryptoS vaults on five chains, including Base. The protocol is winding down, so here is how Base users can withdraw and clean up approvals.
Crypto Support & Research Desk
Quick answer: ACryptoS, a yield vault protocol on Base, Arbitrum, BNB Chain, Polygon and Optimism, was exploited on 8 November 2026 for about $665,000 across 77 vaults. Deposits are disabled and withdrawals remain open while the project winds down. If you hold ACryptoS vault shares on Base, withdraw through the official interface and then revoke the vault's token approvals.
What happened to ACryptoS
ACryptoS is a yield aggregator that runs automated liquidity vaults. On 8 November 2026 an attacker began draining its vaults. Tech Times reported on 9 November that the exploit took about $665,000 from 77 vaults, that deposits were disabled, and that the project said it would wind down because the team "no longer has enough resources" to keep maintaining it.
Crypto.news, citing SlowMist, put the loss at $665,429 and listed the affected networks as Arbitrum, BNB Chain, Polygon, Base and Optimism. A technical write-up by Panda Security on DEV Community, which draws on the project's post-mortem, says the attack ran from about 02:02 to 16:22 UTC on 8 November across 135 addresses, and that deposits were disabled on every vault by about 16:40 UTC.
How much was taken on Base
According to Panda's per-chain breakdown, 13 of ACryptoS's 18 vaults on Base were hit, with about $69,800 taken on Base. The same write-up says that in one Base vault the exploiter ended up holding almost all of the shares. The team burned those shares on 9 November so that the remaining assets, about 6,187 USDbC, stayed available to legitimate depositors. Roughly 1,800 USDbC had already been withdrawn by the attacker before that.
These Base-specific figures come from one security write-up and the project's post-mortem. Treat them as the best available estimate rather than final numbers.
Why it happened: the reported root cause
ACryptoS vaults that hold two tokens, such as a liquidity position, use a function that accepts a list of deposit amounts, one per token. Panda's analysis says this depositMulti function never checked that the length of the amounts list matched the number of tokens in the vault.
By passing a list with only one amount, an attacker could make the vault value the deposit using just the first token. A small deposit was then counted as if it were much larger, so it minted a large share of the vault. The attacker then used the matching withdrawal function, which pays out across both tokens in proportion to shares, to take far more than they put in. Panda says a test on a forked Polygon vault showed a 10 USDC deposit minting about two-thirds of the vault's shares.
Crypto.news and TokenPost described the bug more simply as missing input validation. Either way, it was a smart contract logic flaw, not a problem with the Base network itself.
Who is affected
- ACryptoS vault depositors on Base and the other four chains. If your vault was among those hit, its share value may now be lower than before.
- Users with open token approvals to ACryptoS vault contracts. The project is shutting down, so those approvals no longer serve a purpose.
- Users of protocols that integrated ACryptoS vaults. Check with those projects directly if your position was routed through ACryptoS.
How to check and withdraw your ACryptoS position on Base
Step 1: Find your position
- Open your wallet on Base and look for ACryptoS vault share tokens.
- Use a block explorer such as Basescan to look up your address and review recent ACryptoS interactions.
- If you are not sure which vault you used, check your past deposit transactions.
Step 2: Withdraw through the official interface only
- Reach ACryptoS through links in its official documentation at docs.acryptos.com, not through search ads or direct messages.
- Confirm the contract address you are interacting with matches the one in your original deposit transaction.
- Withdraw the full balance. The project does not plan to relaunch, so there is no reason to leave funds in a deprecated vault.
Step 3: Revoke token approvals
- After withdrawing, revoke the approvals you gave ACryptoS vault contracts for tokens such as USDC, USDbC or WETH.
- Use a reputable approval checker or your wallet's built-in permissions view.
- Our guide on checking and revoking token approvals on our sister site walks through the process step by step.
Step 4: Record everything
- Save transaction hashes for your deposits and withdrawals.
- Note the value of your position before and after the exploit if you can find it.
- These records will help if the project or a third party ever announces a recovery process.
If a Base transaction seems stuck while you withdraw, see our guide to a Coinbase-to-Base transaction that is still pending. Faster block times after the recent Base Denim upgrade mean most withdrawals confirm quickly once submitted.
Is compensation coming?
Not as far as the public record shows. Tech Times and crypto.news reported that ACryptoS offered the attacker a 10% bounty in exchange for returning the rest. Panda said it could not confirm that offer in the post-mortem and saw no returned funds at the time of its last check. No deadline for withdrawals has been published, but the project has said it is winding down, so it is safest to withdraw as soon as possible.
How to judge DeFi vault risk on Base in future
Exploits like this one are hard for ordinary users to spot in advance, but a few habits reduce exposure:
- Check audits and their dates. An audit from years ago may not cover newer vault types or upgrades.
- Watch for maintenance signals. Infrequent updates, quiet social channels or a small team can mean fewer people watching the code. ACryptoS itself said it lacked the resources to keep maintaining the protocol.
- Spread deposits. Keeping all your Base yield in one protocol concentrates smart contract risk.
- Limit approvals. Approve only the amount you plan to deposit rather than unlimited spending.
- Follow official channels. Projects usually post incident updates on their verified X account and documentation first.
None of these steps guarantees safety, but together they make it less likely that a single bug wipes out a large share of your funds.
What to avoid
- Do not deposit more to try to average out losses. Deposits are disabled for a reason.
- Do not trust copycat sites. Wind-downs are prime time for phishing sites that imitate the real interface.
- Do not leave approvals open to contracts that are no longer maintained.
Projects winding down on Base is not new. Our guides on the Horizen L3 shutdown and ZEN/ETH returns on Base and the AERO token migration cover similar steps for other protocols.
Frequently asked questions
Was the Base network hacked in the ACryptoS exploit?
No. The exploit targeted a bug in ACryptoS's own vault contracts. Base itself, its sequencer and its official bridge were not affected.
How much was stolen from ACryptoS?
About $665,000 across 77 vaults on five chains, according to SlowMist figures. Security researchers estimate about $70,000 of that was taken from vaults on Base.
Can I still withdraw from ACryptoS vaults?
Yes. The project disabled deposits but kept withdrawals open. Withdraw through the official interface linked from docs.acryptos.com and revoke approvals afterward.
Will ACryptoS reimburse users?
No reimbursement plan has been announced. The team said it is winding down the protocol. A 10% bounty was reportedly offered to the attacker, but no returned funds have been confirmed.
Someone messaged me offering to recover my ACryptoS funds. Is it real?
Treat it as a scam. Legitimate projects announce recovery processes publicly through official channels and never ask for seed phrases, private keys or upfront fees.
Conclusion
The ACryptoS exploit was a contract-level bug, not a Base network failure, but Base users with vault positions still need to act. Withdraw what remains through the official interface, revoke approvals, keep records of your transactions, and ignore anyone promising recovery for a fee.
Base Coin Support is an independent educational site and is not affiliated with Coinbase, Base, ACryptoS or any exchange. This article is general information, not financial advice. We will never ask for your seed phrase, private keys, passwords or 2FA codes.
Regulatory & Financial Risk Disclosure
The opinions, research, and analysis expressed in this publication are solely for educational and informational purposes and do not constitute investment, financial, legal, or tax advice. Digital asset markets are speculative and volatile. Past performance does not indicate future results. Always perform independent due diligence.
About the Author
Crypto Support & Research Desk
Crypto Support Desk publishes practical, source-led guides to exchange, wallet, network and on-chain service changes. Information is checked against primary or reputable security sources and is not investment advice.