Nemo Protocol Explains $2.6 Million Exploit Caused by Code Vulnerabilities

2025/09/11 18:05

TLDR

  • Nemo Protocol’s $2.6 million exploit stemmed from unaudited code and developer errors.
  • The vulnerabilities were introduced in January and led to unauthorized access and fund theft.
  • Nemo has paused operations, patched the issues, and is working on compensating affected users.
  • The attack exploited a flash loan function and query flaw, draining assets from liquidity pools.

Nemo Protocol, a DeFi platform built on the Sui blockchain, has outlined the causes of its $2.6 million exploit earlier this month. The platform revealed in a post-mortem report that the attack was due to two vulnerabilities introduced into its code by a developer and deployed without proper auditing. The breach, which occurred on September 7, exploited flaws that allowed unauthorized access and manipulation of its smart contract.

Vulnerabilities in the Codebase

The Nemo team explained that the exploit stemmed from two primary issues within the code. First, an internal flash loan function was accidentally exposed to the public. Second, a flaw in a query function enabled unauthorized state changes within the contract. These vulnerabilities were introduced in January 2023, after the protocol received an initial audit report from blockchain security firm MoveBit. Despite the warnings, one of Nemo’s developers incorporated new, unaudited features into the codebase and deployed them to the mainnet.

Notably, the governance structure of the protocol relied on a single-signature address for upgrades, which allowed the unvetted code to be deployed. The team acknowledged that this system failed to prevent risky updates from being introduced. Furthermore, despite a security warning from Asymptotic in August regarding a separate vulnerability, the team did not take immediate action to address the issue.

Exploit Mechanics and Fund Movement

The attacker exploited the combination of the flash loan function and the query function vulnerability to manipulate the contract’s internal state. This enabled the unauthorized draining of assets from the SY/PT liquidity pool. The stolen funds were moved from the Sui network to Ethereum via the Wormhole CCTP bridge. As of now, the majority of the stolen assets remain in a single address.

In response to the breach, Nemo Protocol has paused its core functions to prevent further damage. The team has already patched the vulnerabilities and submitted the updated code for an emergency audit. They are working closely with security teams on the Sui blockchain to trace the stolen funds. Furthermore, the team is planning to compensate affected users.

Acknowledging the Failures

Despite multiple audits and safety measures, Nemo acknowledged that it had relied too heavily on past assurances without maintaining rigorous scrutiny at every step. The report stated that the team’s failure to catch these vulnerabilities during the development phase contributed to the exploit.

Nemo Protocol, a yield infrastructure platform, focuses on yield tokenization and aims to improve DeFi interactions. This breach has raised concerns about the platform’s code integrity, but the team is taking steps to address the issues and prevent future attacks.

The post Nemo Protocol Explains $2.6 Million Exploit Caused by Code Vulnerabilities appeared first on CoinCentral.

Clause de non-responsabilité : les articles republiés sur ce site proviennent de plateformes publiques et sont fournis à titre informatif uniquement. Ils ne reflètent pas nécessairement les opinions de MEXC. Tous les droits restent la propriété des auteurs d'origine. Si vous estimez qu'un contenu porte atteinte aux droits d'un tiers, veuillez contacter service@support.mexc.com pour demander sa suppression. MEXC ne garantit ni l'exactitude, ni l'exhaustivité, ni l'actualité des contenus, et décline toute responsabilité quant aux actions entreprises sur la base des informations fournies. Ces contenus ne constituent pas des conseils financiers, juridiques ou professionnels, et ne doivent pas être interprétés comme une recommandation ou une approbation de la part de MEXC.
Partager des idées

Vous aimerez peut-être aussi

JPMorgan Chase: Strategy was "snubbed" by the S&P 500 Index, sounding the alarm for corporate Bitcoin reserves

JPMorgan Chase: Strategy was "snubbed" by the S&P 500 Index, sounding the alarm for corporate Bitcoin reserves

PANews reported on September 11th that, according to CoinDesk, despite meeting the technical eligibility criteria, Strategy (MSTR)'s application to join the S&P 500 index was rejected. JPMorgan Chase believes this indicates the market's growing caution toward companies acting as Bitcoin funds. The decision not only frustrated Strategy, but also dealt a blow to companies that have followed its model of accumulating Bitcoin on their balance sheets. JPMorgan Chase pointed out that the inclusion of Strategy in other major benchmark indices, such as the Nasdaq 100 and MSCI, has quietly opened a backdoor for Bitcoin to enter retail and institutional portfolios, but the S&P 500's decision may mark the limit of this trend and may prompt other index providers to reconsider the inclusion of existing Bitcoin-weighted companies. JPMorgan Chase noted that Nasdaq's requirement for shareholder approval before issuing new shares to purchase cryptocurrencies has exacerbated pressure. Strategy has abandoned its commitment to non-dilution and is willing to issue shares at low price-to-earnings ratios to purchase cryptocurrencies. Currently, corporate crypto reserves are facing weak stock prices, slowing issuance, and waning investor interest, raising questions about the sustainability of their models. Investors and index providers may favor crypto companies with actual operating businesses.
Partager
PANews2025/09/11 20:10
Partager