Umbra Disables Website After $800,000 in Stolen Funds Moved Through Protocol

Umbra shut down its hosted frontend after funds tied to the Kelp exploit moved through the privacy protocol, while stating that transactions remain traceable on-chain and core contracts are still operational.

Fact Check
The claim is supported by multiple independent secondary reports. 'Umbra shuts front end after hackers move stolen funds through protocol' says Umbra took the front end offline after about $800,000 in stolen funds passed through the protocol and that the smart contracts remain operational. Odaily's '隐私协议 Umbra 关闭前端以阻止攻击者转移 Kelp 相关被盗资金' matches the same key details and specifically says the related transactions remain traceable on-chain. PANews' '隐私协议Umbra关闭前端以阻止Kelp攻击者利用其转移资金' independently repeats those points and notes the hosted frontend was placed into maintenance mode. Confidence is only medium because no direct Umbra primary post or official site statement was retrievable in this run, and the exact upstream source appears to be cited secondhand.
    Reference
Summary

Umbra said it disabled its hosted frontend website after about $800,000 linked to the Kelp protocol exploit was transferred through its privacy protocol. The move followed the Kelp attack, which resulted in losses of more than $280 million. Umbra stated that its transactions remain traceable on-chain and that its smart contracts were not shut down, meaning the protocol itself remains accessible through its self-hosted open-source frontend.

Terms & Concepts
  • smart contracts: Self-executing blockchain code that continues to run on-chain without relying on a project’s hosted website.
  • frontend: The user-facing interface used to access a crypto protocol; Umbra disabled its hosted version while leaving self-hosted access available.
  • on-chain: Activity recorded on a blockchain, allowing transactions to be publicly traced through blockchain data.