AI-assisted summary, reviewed by NullTX editors.

ACryptoS lost about $665,000 across 77 vaults on five chains after a missing input check let attackers mint most of a vault's shares with a tiny deposit. Five exploiter addresses have been published.A vault is supposed to hand out shares in proportion to what you put in. ACryptoS's vaults handed out most of the pool for the price of one small token deposit, because a function never checked how many amounts it had been given.

ACryptoS, a DeFi yield aggregator, disclosed on November 9 that its vaults had been exploited for roughly $665,000 across 77 vaults on five chains. In its announcement on X, the project blamed a lack of input validation that let an attacker mint the majority of a vault's shares by depositing only a minimal amount of tokens.

It has been revealed that it then disabled deposits, left withdrawals open, remarked it can no longer maintain the project and offered the attacker a 10% bounty in exchange for returning the funds.The most specific technical account comes from SlowMist's hack database. It traces the bug to the `depositMulti` function, where the length of the amounts array was never verified against the number of tokens. An attacker could deposit a tiny amount of a single token, receive the vast majority of vault shares and then withdraw a proportional share of both tokens. SlowMist lists the affected chains as Arbitrum, BSC, Polygon, Base and Optimism.

Industry observers note that multi-token vaults, like those behind liquidity-pair strategies, take deposits in more than one asset. A function such as `depositMulti` receives a list of amounts, one for each token the vault holds. The contract then values that bundle against the pool and issues shares accordingly.The safeguard is basic: the number of amounts supplied must equal the number of tokens in the vault. When the two don't match, the contract is working from incomplete or mismatched input, and its valuation logic can behave in ways its authors never intended. According to SlowMist, that check was absent.How ordinary this flaw is deserves a mention. It isn't an oracle trick or a flash-loan puzzle. It's a missing `require` statement on a public function, exactly the kind of slip that audits and fuzzing exist to catch.

Recent findings suggest that A simplified illustration shows how the numbers work. ACryptoS's published analysis doesn't include the exact contract code, so what follows describes the mechanics of this class of bug, not a line-by-line reconstruction.In a healthy vault, shares are minted in proportion to the deposit's share of the pool. Suppose a vault holds $10,000 in assets and has issued 10,000 shares. A $1 deposit should mint about 1 share, or 0.01% of the supply, and redeeming those shares returns about $1.Now let mismatched inputs throw off the mint calculation. The ratio of deposit to pool collapses or inverts, and the contract might credit the attacker with 90,000 latest shares for that $1. The attacker then holds 90,000 of 100,000 shares, or 90% of the supply. Because withdrawals pay out pro rata, redeeming those shares returns about 90% of each token in the pool, roughly $9,000, for a $1 deposit.The reported total fits that scale. Spread across 77 vaults, $665,000 averages about $8,600 per vault, which points to relatively small pools drained repeatedly rather than a few large ones. It also explains why the attack could be repeated mechanically: each vault offered the same function and carried the same flaw.

Recent findings suggest that yield aggregators usually deploy vaults from a shared template, and each vault's strategy contract inherits the same logic. As a result, one unchecked function in that template turns into one exploit multiplied by every deployment. Seventy-seven vaults on five chains is what that multiplication looks like.The setup also keeps the cost of attack low. Once the flaw is understood, a script can walk through every vault on every chain, call the same function and withdraw. On top of that, ACryptoS indicates the stolen funds have been moved through several cross-chain protocols, a pattern that complicates recovery.

ACryptoS has asked exchanges and bridges to flag five exploiter addresses in a follow-up post on X:.

The request targets exit points. With the stolen funds hopping across chains, the places where they are most likely to be cashed out or bridged are the ones best placed to slow the attacker down. These are EVM addresses and the exploit spanned five networks, so anyone investigating should check each address on Arbitrum, BSC, Polygon, Base and Optimism.The rest of the response is blunt. Deposits are disabled and withdrawals remain open, with users urged to pull their assets rapidly. ACryptoS cited an inability to keep maintaining the protocol, so further patching is unlikely. Remaining users should assume vault pools may be thin, withdraw while the function still works and revoke token approvals granted to ACryptoS contracts afterward. A 10% bounty is a common offer in situations like this, but whether the attacker responds is unknown, and users shouldn't strategy around a recovery.

Sources indicate that for developers, the lessons are narrow and testable. Every public function that takes an array should check its length against the data it is supposed to match. Share-minting should be tested against an invariant: the value of shares issued can never exceed the value deposited. The ERC-4626 standard defines how vault share accounting should behave, and fuzz tests built on its rules would likely have flagged this.Sunsetting a protocol needs a plan as well. A deprecated vault that still holds funds and still exposes live deposit functions is an open target. Pausing deposits and migrating balances before the maintainers leave costs little compared with leaving an unmaintained contract holding user money.For customers, the story repeats a familiar warning. Small, older yield protocols with shrinking teams are the ones most likely to carry unpatched code. This incident has less to do with a clever attack than with maintenance running out before the code was safe, so the best protection is to treat vault deposits in aging projects as temporary.

Sources indicate that disclosure: This is not trading or investment advice. Always do your research before buying any cryptocurrency or investing in any services. Follow us on XΒ @nulltxnews.

According to recent reports, loopscale's Genesis Vault lent 4,597 SOL against a single kySOL token that the protocol valued as ten zBTC. The decimal mismatch behind it is the most instructive part of the incident, and a second attack path reveals how far the probing went.One token worth roughly $120 was all a Loopscale vault held when it handed out 4,597 SOL, because the protocol read tha….

AKT stakers are close to approving Akash's move from Cosmos to Solana, with Mintscan projecting a pass at 97.2% yes as voting enters its final hours. But a yes on Proposal 346 opens a door rather than completing a move. Before a single AKT reaches Solana, two independent audits and at least two more on-chain votes still have to happen.The summary going aroun….

Recent findings suggest that daily pool data highlights Sprout holders moved more than 300 ZEC out in a September rush, then almost stopped. The last withdrawal was on October 19. Unless someone acts in the next few days, nearly all of what remains will be unspendable at block 3,543,405.Most coverage of Zcash's upcoming Sprout freeze quotes the same figure, about 22,000 ZEC. That number is a….

In a recent development, the OCC's final GENIUS Act rule sets a 5% cash floor and a 40% cap on any one counterparty. The Fed's open proposal uses neither figure, and its comment window runs until November 30. Issuers now face two sets of reserve rules that share a redemption deadline and differ on almost everything else.Ask a stablecoin issuer what its reserves must look like in 202….

One email a week with our latest explainers and the news behind them.

More explainers and analysis from NullTX.

β†’ Read original article