📈 Get daily crypto insights that make you smarter about your money

zkLend Suffers $9.57 Million Exploit Through Decimal Precision Vulnerability on Starknet

The Starknet-based lending protocol zkLend suffered a devastating security breach in February 2025, losing approximately $9.57 million in digital assets after an attacker exploited a subtle decimal precision vulnerability in the platform’s smart contract code. The incident, which sent shockwaves through the Layer 2 DeFi ecosystem, highlights the persistent risks that even audited protocols face when handling complex mathematical operations across different token decimal configurations.

The Exploit Mechanics

The attacker targeted a critical flaw in how zkLend’s accumulator system handled decimal precision across different token types. Starknet, unlike Ethereum’s EVM, uses a Cairo programming model with its own arithmetic rules, and the vulnerability emerged from the interaction between token decimals and the protocol’s interest rate accumulator calculations. The exploit allowed the attacker to manipulate the accumulator to artificially inflate their collateral value while deflating their debt, creating a massive arbitrage opportunity that drained the protocol’s liquidity pools.

Specifically, the attacker used a flash loan to amplify their position, then triggered the decimal precision mismatch to withdraw significantly more value than they had deposited. The attack was executed in a single transaction, making it impossible for the protocol’s monitoring systems to intervene before the damage was done. With Bitcoin trading around $95,500 and Ethereum near $2,670 at the time, the stolen assets represented a substantial loss for the protocol’s users.

Affected Systems

The exploit directly impacted zkLend’s lending pools on Starknet, with multiple token markets affected including major stablecoins and wrapped assets. The protocol was forced to pause all operations immediately after detecting the breach. zkLend’s native ZEND token also experienced significant downward pressure as news of the exploit spread across social media and crypto news outlets.

The broader Starknet DeFi ecosystem felt the impact as well, with total value locked across the network dropping as users rushed to withdraw funds from other protocols out of caution. The incident raised uncomfortable questions about the maturity of Cairo-based smart contract development and whether existing audit practices adequately cover the unique risks of Starknet’s execution environment.

The Mitigation Strategy

zkLend’s response team acted swiftly to contain the damage. The protocol offered a 10% white hat bounty to the attacker, urging them to return the stolen funds. The team also engaged multiple blockchain security firms, including SlowMist and BlockSec, to conduct a thorough post-mortem analysis. Their findings confirmed that the decimal precision vulnerability was the root cause, with the exploit bearing similarities to the earlier EraLend hack on the same network.

For the broader ecosystem, the incident underscored the need for specialized audit tools that can detect decimal precision issues in Cairo smart contracts. Standard EVM-focused audit methodologies may not catch these types of vulnerabilities, creating a dangerous blind spot for protocols building on Starknet and similar non-EVM chains.

Lessons Learned

The zkLend exploit serves as a stark reminder that decimal handling remains one of the most treacherous areas of smart contract development. Even small discrepancies in how tokens with different decimal places interact within lending protocols can create exploitable conditions. Development teams must implement rigorous testing specifically for decimal edge cases, including fuzzing with extreme values and formal verification of mathematical operations.

The incident also highlights the importance of layered security approaches. While audits are essential, protocols should complement them with real-time monitoring systems that can detect anomalous accumulator behavior, circuit breakers that pause operations when unusual withdrawal patterns emerge, and insurance mechanisms that can compensate users in the event of a successful exploit.

User Action Required

Users who had funds deposited in zkLend should monitor the protocol’s official communication channels for updates on the recovery process and any potential compensation plans. For users of other Starknet DeFi protocols, this incident serves as a reminder to evaluate the security measures in place, particularly around decimal handling and accumulator mechanisms. Diversifying across multiple protocols and chains remains one of the most effective strategies for minimizing the impact of any single exploit.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Always conduct your own research before engaging with any DeFi protocol.

🌱 FOR BUSINESSES BitcoinsNews.com
Reach 100K+ Crypto Readers
Sponsored content, press releases, banner ads, and newsletter placements. Put your brand in front of Bitcoin's most engaged audience.

9 thoughts on “zkLend Suffers $9.57 Million Exploit Through Decimal Precision Vulnerability on Starknet”

  1. decimal precision bugs keep happening because auditors know Solidity inside out but barely understand Cairo. L2 security is only as strong as the audit quality

    1. startup funding vaporized in one transaction. and Starknet audits somehow missed basic decimal math. Cairo is a different beast from Solidity

      1. cairo audits are still in their infancy compared to solidity. the tooling just isnt there yet for catching these edge cases

        1. Mira Novak the tooling gap between Cairo and Solidity is massive. Echidna and Slither dont even have proper Cairo equivalents yet

    1. Been through worse exploits. The real question is: how long until they patch this and do people come back?

      1. sarah K people came back after bigger exploits on ethereum mainnet. question is whether starknet defi TVL ever recovers to levels where this matters

  2. flash loan to amplify a decimal precision exploit is clean execution. one transaction, 9.57M gone. the accumulator design was the weak link

Leave a Comment

Your email address will not be published. Required fields are marked *

BTC$63,962.00-1.4%ETH$1,740.76-1.7%SOL$71.19-1.5%BNB$588.86-2.1%XRP$1.17-2.2%ADA$0.1666-1.4%DOGE$0.0847-1.5%DOT$0.9796-3.2%AVAX$6.63-2.9%LINK$7.99-2.4%UNI$3.16-13.4%ATOM$1.83-7.4%LTC$44.13-2.6%ARB$0.0848-2.1%NEAR$2.22-2.6%FIL$0.7967-2.2%SUI$0.7483-5.4%BTC$63,962.00-1.4%ETH$1,740.76-1.7%SOL$71.19-1.5%BNB$588.86-2.1%XRP$1.17-2.2%ADA$0.1666-1.4%DOGE$0.0847-1.5%DOT$0.9796-3.2%AVAX$6.63-2.9%LINK$7.99-2.4%UNI$3.16-13.4%ATOM$1.83-7.4%LTC$44.13-2.6%ARB$0.0848-2.1%NEAR$2.22-2.6%FIL$0.7967-2.2%SUI$0.7483-5.4%
Scroll to Top