Namada’s Multi-Asset Shielded Pool has reportedly been drained for roughly $600,000, with shielded IBC assets swept from the privacy chain while an indexer still showed funds in place. A F12s
Namada’s Multi-Asset Shielded Pool has reportedly been drained for roughly $600,000, with shielded IBC assets swept from the privacy chain while an indexer still showed funds in place.
A F12sec alert identified ATOM, USDC, OSMO, TIA and NYM among the assets removed from the MASP. The security account said the indexer continued displaying balances, while live RPC checks showed the pool at zero.
The mismatch made the incident harder to see from normal dashboard views. In a transparent DeFi exploit, balances, transfers and vault changes can usually be checked quickly through explorers and direct contract reads. In Namada’s case, the affected assets were inside a shielded environment, where privacy design and stale indexing appear to have delayed visibility into the drain.
Namada is built around a unified shielded set that allows users to hold and move different assets with privacy, including cross-chain assets brought in through IBC. Its MASP is designed to let multiple asset types share one shielded pool, rather than requiring separate shielded pools for each token.
That model is central to Namada’s privacy pitch. The Multi-Asset Shielded Pool lets asset types remain shielded inside transactions, with exceptions where transparent balance changes are required. For normal users, the result is private cross-chain asset movement. For incident response, the same design can make live balance verification more dependent on reliable node queries and accurate indexer state.
The reported drain did not involve only Namada’s native asset. F12sec listed Cosmos assets including ATOM, OSMO and TIA, plus USDC and NYM, pointing to an IBC asset event rather than a single-token accounting issue.
The Namada report lands shortly after another Cosmos-connected bridge incident. Axelar recently disabled Secret Network connections after a $4.67 million IBC asset drain, while stating that Axelar’s core protocol was not affected. That case centered on assets bridged from Axelar to Secret through a specific Secret-side route.
The Namada case is different because the flagged issue sits inside a privacy pool rather than a standard transparent bridge route. The common thread is cross-chain asset exposure through narrower integration layers, where the affected path can be smaller than the headline ecosystem but still hold real user funds.
Recent DeFi incidents have also shown how accounting and visibility gaps can matter as much as the headline exploit size. mySwap’s Starknet CL pools were drained for roughly $305,000 after a fake token distorted shared-vault accounting, leaving another example of funds moving through a specific logic path rather than a broad protocol-wide compromise.
The most unusual part of the Namada report is the visibility gap. F12sec said the indexer still showed funds in the MASP while live RPC returned a zero balance. That means users checking the wrong data layer could see a stale pool state even after the assets had already been swept.
No official Namada postmortem, recovery plan or final loss confirmation had been published at the time of writing. The incident remains based on the F12sec technical alert, with the reported status showing roughly $600,000 in ATOM, USDC, OSMO, TIA and NYM removed from Namada’s MASP and live RPC data showing the shielded pool balance at zero.
The post Namada MASP Drain Exposes $600K Blind Spot In Shielded Assets appeared first on Crypto Adventure.
