TechFlow Logo
Login/ Sign up
ETH Gas
Gwei
Fear
gas
Cronos, Fogo, and Cosmos Halt Operations in Succession: The Final Line of Defense in the Crypto World Is "Pulling the Plug"

Cronos, Fogo, and Cosmos Halt Operations in Succession: The Final Line of Defense in the Crypto World Is "Pulling the Plug"

2026.08.31
Share
The security architecture of the current generation of crypto networks is still far from ready to support their claimed vision of trustlessness.

Written by: Xiao Bing

On August 30, Cronos validators froze the entire blockchain.

Twenty-four hours earlier, Fogo did the same. A week prior, Cosmos Labs sent an emergency notice to all chains running its EVM module: upgrade or shut down.

Three completely different attack vectors, three different on-chain governance structures, but ultimately all pointing to the same emergency plan: shutting down the chain.

When a real crisis hits, the "last line of defense" for decentralized networks isn't much different from traditional internet companies' contingency plans: they both just pull the plug.

$75 Million, 20 Minutes

The events on Cronos carry a textbook sense of déjà vu.

The attacker targeted Tectonic, the largest and nearly only lending protocol on Cronos, with a TVL of approximately $121.7 million, accounting for 46% of the entire chain's DeFi locked value. The leverage pivot point was Tectonic's governance token, TONIC, an asset with extremely thin liquidity.

The method was old-school: inflate the price of TONIC by roughly 100x in about 20 minutes, then use these "inflated" tokens as collateral to borrow real value—major liquid assets like cbBTC, USDC, and WETH—from the lending pools.

On-chain researcher Weilin Li estimated that the attacker held approximately 364.6 trillion TONIC. Calculated against a 20% collateral factor, their position post-manipulation needed a valuation of roughly $375 million to support a loan of about $75 million. This figure aligns perfectly with the 100x price inflation.

Cronos validators reacted swiftly. By the time the chain was frozen, the attacker had only managed to bridge around $6 million to Ethereum, leaving the remaining $60 million stranded on the chain that had ceased block production.

Crypto.com CEO Kris Marszalek immediately issued a statement on X, confirming that Crypto.com's app and exchange remained unaffected while its security team assisted in the investigation.

This was a successful damage control operation, which also exposed an awkward reality: Cronos's ability to coordinate such a rapid shutdown stems precisely from its small validator set.

Built on Tendermint consensus, Cronos caps its validators at 100, with even fewer actually active. This makes emergency coordination highly efficient, yet renders the term "decentralization" quite nuanced.

In October 2022, Avraham Eisenberg extracted over $100 million from Solana's Mango Markets using virtually the exact same tactic.

The playbook was identical: manipulate the price of a low-liquidity MNGO token, then borrow real assets against artificially inflated collateral. Eisenberg was later arrested and convicted of commodity fraud. Legal precedent has now been set: even if an attacker technically adheres to a protocol's own rules, manipulating DeFi token prices constitutes a criminal offense.

Just three days ago, Base network lending protocol Moonwell suffered losses of approximately $8.7 million due to an entirely identical attack vector. The attacker manipulated the price of the low-liquidity MAMO token to borrow cbBTC and USDC. This marks Moonwell's third oracle-related security incident within 11 months.

The Mango Markets script has been running from 2022 into 2026, switching across three chains and three token names, yet the core logic remains completely unchanged.

Lending low-liquidity tokens as collateral on DeFi protocols is akin to a bank accepting an unauthenticated painting as pledge: the stated price means nothing; it only counts if it can actually be sold.

Chain Running Normally, Then Shut Down 15 Hours Later

Fogo's situation is even more intriguing.

On the evening of August 29 (9:13 PM ET), the Fogo Foundation posted on X stating that an unknown attacker "breached" the foundation, resulting in 400 million FOGO tokens being transferred to bad actors. The foundation notified exchanges and law enforcement agencies, while emphasizing that "the Fogo blockchain itself remains unaffected and continues to operate normally."

400 million FOGO represents 4% of the genesis total supply (10 billion tokens), but over 10% of the current circulating supply. At FOGO's price of roughly $0.0075 at the time of the incident, this valued around $3 million. While not a massive sum, having 10% of the circulating supply suddenly fall into an attacker's hands is enough to pose a systemic risk for an L1 with an already modest market cap.

Interestingly, Bitget reacted first, halting FOGO deposits and withdrawals about an hour before Fogo's official disclosure under the guise of "wallet maintenance." KuCoin followed suit shortly after, proving that exchanges possess a sharper nose than project announcements.

But what happened next was the real crux: roughly 15 hours after the foundation claimed the "chain was running normally," Fogo took down its mainnet. The announcement stated the halt was to prevent further transfers of affected assets, with validators set to upgrade the network to "restrict addresses associated with unauthorized activity."

The shift from "everything is fine" to "pulling the plug" barely lasted a night's sleep.

The foundation has yet to disclose the attack vector or explain whether the stolen tokens originated from operational reserves or financial holdings. More critically: if Fogo can shut down the entire chain and freeze specific addresses through validator coordination, how is its degree of decentralization actually defined?

One Bug, Six Chains, Four Months

The story behind Cosmos EVM operates on another dimension of terror.

This wasn't an issue with a single specific chain, but a supply-chain-level vulnerability rooted in a shared codebase. Cosmos EVM is an open-source module that enables Cosmos SDK-based blockchains to run Ethereum-compatible smart contracts. Any chain adopting this module inherited the exact same code flaw.

The flaw was an integer underflow error: when a vesting account's staked amount exceeded its spendable balance, the system didn't throw an error but instead allowed the balance to "wrap around" to a near-mathematical infinity close to 2^256. Attackers required no admin privileges; by constructing a single specialized transaction, they could grant any account a seemingly infinite balance overnight.

The timeline is deeply unsettling.

On April 25, a researcher reported the defect through Cosmos Labs' bug bounty program. The QA team concluded that the production network was unaffected. The fix was pushed as a routine update, unmarked as security-critical, with no CVE published, no advisory released, and downstream chain operators left uninformed.

On August 13, internal team confirmation revealed that all Cosmos EVM chains were vulnerable. The patched version went live on August 19. Just one day after the patch release, the first attack struck MANTRA. Within the following five days, the exploit spread across six chains, including MANTRA, TAC, and KiiChain, resulting in total losses of approximately $5.72 million.

During the incident response, Cosmos Labs reached out to 40 chains and uncovered 11 Cosmos EVM deployments that weren't on their registration list at all. In an ecosystem boasting over 115 public chains, the startling fact that maintainers had no idea who was utilizing their code is arguably scarier than the vulnerability itself.

On August 24, Cosmos Labs issued a public statement on X recommending that all chains running the Cosmos EVM module require validators to shut down. Since the fix was state-breaking, it demanded coordinated upgrades; chains unable to upgrade immediately were advised to simply take their chains offline.

This wasn't the first time. In January 2026, attackers exploited an ICS20 precompile vulnerability within the same codebase, stealing approximately $7 million from Saga's EVM network. Same codebase, same year, two supply-chain-level security breaches.

The shared model of open-source software offers immense efficiency advantages, but it also means one bug can propagate through an ecosystem like an infectious disease. The traditional software industry handles this with mature mechanisms like CVE identifiers, mandatory security advisories, and downstream patch windows. Cosmos Labs bypassed almost all of these steps during this incident.

The Same Attribute, Two Different Assessments

When reporting on the Cronos shutdown, BeInCrypto cited a precise formulation: A chain that can be turned off is simultaneously a chain from which funds can be recovered.

Following Cronos's chain halt, the CRO token actually rose by approximately 4-5%. The market is pricing in "successful damage control." Roughly $60 million in stolen assets remain trapped on-chain; if validators opt for a rollback or blacklisting, these funds might be recovered. Yet Tectonic depositors have received no repayment commitments to date.

After Fogo halted operations, the FOGO price plummeted 18-20%. Whether the 400 million tokens held by the attacker can be frozen hinges on what "restricting addresses" technically entails, a detail Fogo has yet to clarify. Compounding the issue, a new unlock of approximately 1.54 billion FOGO tokens (15.44% of total supply) is scheduled for September 26, and this temporal coincidence leaves market confidence even more fragile.

In the Cosmos EVM case, MANTRA resumed block production roughly 30 hours after the halt, claiming user balances were unaffected. TAC paused at block 24,671,475 on August 22 and remained offline at press time. KiiChain confirmed 18 attacks, resulting in losses of approximately 148 million KII.

Faced with the same vulnerability, these three chains met three entirely different fates.

In the first half of 2026, Blockaid reported that losses from on-chain security incidents surpassed $1.1 billion, spanning 212 events. CertiK's figures are even higher: 344 incidents totaling roughly $1.31 billion in losses, exceeding the full-year total of 2025.

These numbers paint a stark reality: security issues across crypto networks aren't improving; they are deteriorating.

Attack vectors continue to recycle and evolve, but defensive mechanisms haven't kept pace. Oracle pricing for low-liquidity tokens and security audits for shared codebases remain two systemic vulnerabilities.

The sole fallback option is to "shut down the chain," which is itself a signal: the security architecture of this generation of crypto networks is nowhere near ready to bear the trustless vision they profess. As for what happens after the halt—rollback, blacklisting, or restoring service as-is—each option carries its own consequences and precedential effects. This isn't merely a technical choice; it's a governance decision, and governance has always been the least publicly discussed aspect of the crypto world.