Privacy-focused public blockchain Namada has reported an exploit in the Namada protocol. The incident was recorded by Foresight under its “whale movement” category, with the entry stating that about 228,500 ATOM have been transferred out. Namada’s official account, @namada, posted a short statement on X confirming that the protocol had been exploited and that the team is investigating the matter with relevant parties involved.
In the X post published at 9:33 on June 20, 2026, Namada wrote: “There’s been an exploit in the Namada protocol. We are investigating the issue and are involving the relevant parties. If you are the white hat hacker behind this exploit, please get in touch with us.” The statement confirms the occurrence of the exploit, the start of an investigation, and the team’s outreach to any white hat hacker connected to the incident. It does not provide technical details, an attack vector, affected account information, or a remediation schedule.
The Foresight item adds the key asset movement figure: about 228,500 ATOM have been transferred out. The input information identifies ATOM as the asset involved and gives the amount as approximately 228,500 tokens. No transaction hash, recipient address, number of transfer batches, on-chain timestamp, or subsequent movement of the assets is included in the available entry.
The official post also shows several page-level data points. The X link is https://x.com/namada/status/2068265932368347358, and the post displayed 5,318 views along with a “Read 8 replies” prompt. The captured content also includes frontend fragments such as host, number-flow-react, span, digit, and symbol, as well as the numbers 8, 4, 20, and 7. These appear as part of the page capture and do not add further details about the exploit itself.
The news record lists its publication time as 2026-06-20T10:16:59.000Z and its detection time as 2026-06-20T15:00:54.379Z. It also records DelayMinutes as 284 and FreshnessScore as 8. The SourceType is marked as api_json, ArticleFetchStatus was shown as queued_without_extra_fetch_to_avoid_timeout, and QueueLengthAfterPop was 42. The record later indicates FullContentFetched as true, with FetchedFromUrl matching the Namada X post.
Based on the disclosed information, the confirmed facts remain limited to the protocol exploit, the investigation by Namada, the involvement of relevant parties, the white-hat contact request, and the Foresight-reported transfer of about 228,500 ATOM. No additional claims about the method of attack, the identity of the actor, the status of recovery, or the final destination of the transferred ATOM are included in the source material.