Notional Finance has become the latest DeFi protocol hit by a smart contract exploit after an attacker reportedly drained approximately $1.7 million in DAI and USDC from a V1 escrow contract. The incident surfaced on September 4, following onchain analysis of transactions that took place a day earlier.

Security researchers initially identified approximately 69,000 DAI and more than 1.65 million USDC leaving the affected contract. The assets were subsequently converted into roughly 689 ETH before being deposited into Tornado Cash.

How the Notional Finance Exploit Worked

Notional's older V1 architecture represents fixed-rate lending and borrowing positions using fCash, where positions effectively represent future claims or obligations that settle at maturity. A lending position can represent the right to receive assets in the future, while the other side represents the corresponding obligation to pay them.

According to preliminary technical analysis, the attacker exploited the way these positions were created and subsequently evaluated during Notional's free-collateral calculations. The attack reportedly involved two calls to a function used to create paired fCash positions.

The first involved a very small position. Security researchers examining the transaction found that a liability of -1 could effectively disappear because of rounding during the protocol's free-collateral conversion process.

The attacker then created a second position close to the numerical limits of a 128-bit integer. This produced an enormous negative liability, approximately -2^128, alongside a corresponding long position.

The result was economically very different from what the underlying position actually represented. An account carrying an enormous liability could effectively appear to the collateral system as though it had no liability at all.

The @NotionalFinance attack repported by @SpecterAnalyst appears to be caused by an integer overflow.

The ERC1155 implementation allows minting a pair of positions (one long one short) when calling "safeTransferFrom" where from does not have enough position to be transferred.… pic.twitter.com/ZmUpUbg20u

— Weilin (William) Li (@hklst4r) September 4, 2026

Attacker Converts $1.7M Into ETH

Once the manipulated position passed Notional's collateral checks, the attacker reportedly withdrew approximately $1.73 million worth of stablecoins from the affected V1 escrow contract. Onchain investigators identified roughly 69,000 DAI and more than 1.65 million USDC moving from the contract.

The assets were then consolidated and swapped into approximately 689 ETH. The ETH was subsequently deposited into Tornado Cash, making the movement of the funds considerably more difficult to follow beyond the initial attacker-controlled addresses.

EtherWorld previously observed this pattern after the fake eBTC minting attack against Echo Protocol, where compromised assets were used as collateral, converted into more liquid assets and ultimately moved through Tornado Cash.

Speed can matter significantly after a DeFi exploit. Stablecoins may have centralized issuers capable of freezing addresses under certain circumstances, while compromised protocol tokens can become difficult to liquidate as markets react.

Recent incidents also demonstrate why early estimates should be treated carefully. EtherWorld initially covered the reported $9.3 million More Markets lending reserve drain before later reporting that Blockaid revised the financial impact to approximately $410,000.

Why a Small Accounting Error Became Critical

The Notional incident highlights a particularly difficult category of smart contract risk. There does not need to be a visibly broken withdrawal function for a protocol to become exploitable.

If a lending system incorrectly calculates what an account owns, what it owes or how much collateral it has, every function relying on that calculation can potentially become dangerous. If an enormous debt is incorrectly represented as zero, the protocol can reach the wrong conclusion even though the surrounding lending logic works exactly as designed.

A comparable lesson appeared in the Maya Protocol exploit, where multiple weaknesses reportedly interacted to create a larger attack rather than one obvious isolated failure. DeFi's composability can magnify these mistakes further.

During the KelpDAO exploit, unbacked rsETH did not remain confined to the original system. It entered lending markets, where it could be treated as legitimate collateral and used to access liquid assets.

The result became a broader liquidity crisis requiring emergency responses across multiple protocols. Arbitrum later froze more than 30,000 ETH linked to the incident.

#CertiKInsight 🚨

We have seen an ~$1.7M exploit on @NotionalFinance.
https://t.co/luKD7RcbVA

The attacker used two mintfCashPair() calls to create a -2^128 liability, which was truncated to 0 by an unsafe uint128() downcast in free-collateral valuation.

Stay Vigilant! pic.twitter.com/5T7E0XQfWJ

— CertiK Alert (@CertiKAlert) September 4, 2026

What the Exploit Means for DeFi Security

August alone saw attacks involving manipulated collateral, unauthorized token creation, accounting failures, compromised infrastructure and vulnerabilities affecting multiple networks. The Cosmos EVM security incident demonstrated how one shared software dependency could potentially expose several independent blockchains, while Tectonic highlighted the dangers of accepting thinly traded assets as collateral.

Earlier in the year, EtherWorld's review of April 2026 DeFi exploits showed how losses can spread well beyond the original application when compromised assets move through interconnected lending and liquidity systems. Other attacks have required almost no complicated contract manipulation at all.

The Term Finance governance exploit demonstrated how weak governance participation could itself become an attack surface. Together, these cases show why "smart contract security" can no longer mean auditing individual functions in isolation.

Developers and auditors increasingly need to test extreme numerical values, rounding boundaries, token conversions, collateral assumptions, cross-protocol dependencies and unexpected sequences of otherwise valid actions. Until then, the incident offers another reminder that DeFi exploits do not always begin with spectacular cryptographic failures.

To promote your Web3 articles, events, and projects, you may reach out anytime via EtherWorld PR for submissions and collaboration.

Related Articles

1. April 2026 Worst for DeFi: Over $635M Lost in Exploits
2. Rhea Finance Exploit Drains $7.6M
3. KelpDAO Exploit Triggers $290M Crisis Across DeFi
4. DeFi Unites After KelpDAO $292M Hack
5. How $900 Bought Control of an $8.5M DeFi Vault

To follow blockchain news, track Ethereum protocol progress, and read our latest stories, subscribe to our weekly today.

Join the EtherWorld & Avarch Internship Program and build your career in blockchain, content, social media, video, podcast editing, or operations. Send your resume and brief introduction to contact@etherworld.co.