← Radar

Incident case file

Sign in to watch

Namada Shielded Pools — MASP Drained via IBC Behind a Stale Indexer — Silent Hack Discovered by F12 Security

Incident date June 18, 2026

0 views

ActiveNamada (Cosmos ecosystemIBC)Cross-chain (IBC) shielded-pool drain / stale indexer maskingCluster: NAMADA-MASP-2026-06

Estimated loss

$600K

Victims identified

more than ten victims identified
Victim group joining is coming soon.

Investigation

50%

Facts and investigation

Attacker: MISSING — no attacker address or entity publicly identified. Drained tokens were swept out of the Multi-Asset Shielded Pool (MASP) over IBC; the receiving/destination addresses on counterparty chains (Osmosis, Cosmos Hub, etc.) have not been published by any source reviewed.

Funds moved to: MISSING (destination unconfirmed) — F12 Security's analysis confirms the assets were 'swept' from the shielded pool over IBC but does not identify a specific destination address or chain for the outgoing funds. DeFiLlama's TVL chart independently corroborates the drain: Namada Shielded Pools TVL stood at $594,381 on 2026-06-18, and had collapsed to approximately $618 by 2026-06-19 17:47 (later measurements also confirm the low, non-recovering balance, e.g. $618.88 TVL with a live RPC balance o
Discovery credited to F12 Security (@f12sec, F12 Security Labs). The core finding: Namada's public block explorer/indexer continued to display the pre-drain balances long after the underlying live chain state (queryable directly via Namada's RPC) showed the true, drained balances of zero — meaning the hack was effectively invisible to anyone relying on the standard explorer UI ('privacy chain + stale indexer = invisible hack', per F12). F12 verified this directly via raw RPC queries (curl agai

Timeline: T0 (drain occurs some time before public disclosure, most likely 2026-06-18 given DeFiLlama's TVL snapshot of $594,381 recorded that day, collapsing to near-zero by the following day): Attacker(s) drain the liquid IBC-transferable assets (ATOM, USDC, OSMO, TIA, NYM) from Namada's Multi-Asset Shielded Pool (MASP), leaving staked/LSD assets (NAM, stATOM, stTIA, stOSMO, NTRN, Penumbra) untouched. The drain goes undetected by the public-facing block explorer/indexer, which continues to display pre-drain balances. T+public discovery (2026-06-19, 23:15 UTC): F12 Security (@f12sec) publishes the first public disclosure on X, stating Namada's MASP had been drained of ~$600K and that 'nobody noticed' because the indexer showed stale (pre-drain) balances while the live RPC confirmed a true balance of zero. T+minutes: F12 follows up with a token-by-token before/after comparison (indexer figure → live RPC figure) for ATOM, USDC, OSMO, TIA, and NYM, noting that staked assets were left untouched. T+minutes: F12 explains the underlying technical proof for non-technical readers — the raw RPC response's base64-encoded 'AAAA...=' value decodes to all-zero bytes, i.e., balance = 0, whereas a genuinely funded pool would return a real non-zero encoded string. F12 publishes the exact public contract/token addresses used to independently verify the finding via direct RPC query. T+2026-06-20: F12 provides further corroboration, noting that DeFiLlama (which also pulls its TVL data from Namada's live RPC, independent of the stale indexer) showed the same TVL collapse from ~$600K to near-zero over the same period — used by F12 as third-party proof against a community member's suggestion that the discrepancy might be a temporary infrastructure/indexer outage rather than an actual drain. A separate user reports being personally unable to withdraw OSMO holdings from the MASP, corroborating real user impact. Status as of report compilation: incident considered confirmed and unresolved; no official statement, root-cause disclosure, or remediation plan from the Namada project team has been identified in available sources; attacker identity and destination of drained funds remain unknown.

Sources and coverage

Victim testimonies

No testimonies yet.

+ Add my testimony → (coming soon)