Cosmos has asked validators across its ecosystem to stop their chains after a security breach in its EVM layer drained 148.3 million KII tokens. The request went out after teams spotted the shared vulnerability, with several EVM-based chains reporting different levels of disruption.
The shared vulnerability and the halt order
The breach hit the EVM infrastructure that multiple Cosmos chains rely on, meaning a single exploit could cascade across the network. In response, Cosmos issued an urgent call for validators to halt chain operations to stop further losses while the issue was being contained.
That's a heavy ask. Validators are the ones who keep these chains running, and stopping them is not something done lightly. But the 148.3 million KII tokens that vanished made the case for a quick pause.
What the 148.3M KII loss means
The stolen tokens represent a real chunk of value, though the price impact hasn't been spelled out. What's clear is that the loss is tied directly to the EVM breach, and the scale of it—148.3 million—means it's not a small exploit. That's the kind of number that gets people nervous about the security of the whole ecosystem, not just one chain.
Teams across the affected chains are working together to contain the issue. That's the shared security problem: when one EVM layer is compromised, everyone who builds on it has to act as one unit to patch the hole.
Different chains, different damage
Not every Cosmos EVM chain took the same hit. Some faced major disruption, others only partial. But the request to halt chains went out broadly, because the vulnerability is common, even if the exposure isn't.
What caused the breach? The facts don't say. Neither does anyone publicly, at least not yet. The teams are focused on containment rather than pointing fingers.
Where things stand
Right now, the priority is getting the chains back up safely. The halt order is still in place for some validators, and the teams are working through the security issue. The missing piece is the post-mortem: what exactly happened, and what changes will be made to prevent it from happening again. That answer hasn't come out yet.
The next thing to watch for is whether the Cosmos teams will release a detailed breakdown of the breach and a timeline for resuming operations. Until then, the 148.3M KII question hangs over the network.
