Digital Asset
Intelligence
Theme

Search 3CBlock

News, exchanges, regulatory intelligence, reviews and Voices.

Security Incident · ETH Ecosystem

Exactly Protocol Unchecked Input Data: $7.3M Reported Loss

Historical incident record

Incident Overview

The DeFi lending protocol Exactly Protocol was attacked and lost more than 7,160 ETH (approximately $12.04 million). The two contract attackers attack by calling the function kick() multiple times and use the developer contract on Ethereum to transfer deposits to Optimism and eventually transfer the stolen funds back to Ethereum. The root cause of the Exactly Protocol attack is #insufficient_check, the attacker bypasses the permission check in the leverage function of the DebtManager contract by directly passing an unverified fake market address and changing _msgSender to the victim address. Then, in an untrusted external call, the attacker re-enters the crossDeleverage function in the DebtManager contract and steals the collateral from the _msgSender class. Exactly Protocol tweeted that the suspension of the agreement has been lifted, users can perform all operations, and no liquidation has occurred. The hack only affected users using the peripheral contract (DebtManager), the protocol is still functioning normally.

Sources & References

This record presents information attributed to the linked sources. Incident dates describe the original event, not a new report. Reported loss figures reflect the source record and are not current market valuations.

More Security Incidents

View All →
  1. Incident date
    Target

    SwirlLend

    Attack methodRug Pull
    Reported loss$ 460,000
  2. Incident date
    Target

    MetisDAO

    Attack methodAccount Compromise
    Reported lossNot disclosed
  3. Incident date
    Target

    RocketSwap

    Attack methodPrivate Key Leakage
    Reported loss471 ETH
  4. Incident date
    Target

    Balancer

    Attack methodFlash Loan Attack
    Reported loss$ 2,100,000
  5. Incident date
    Target

    Zunami Protocol

    Attack methodPrice Manipulation
    Reported loss$ 2,200,000
  6. Incident date
    Target

    Harbor Protocol

    Attack methodContract Vulnerability
    Reported loss$ 20,000
  7. Incident date
    Target

    Made by Apes

    Attack methodInformation Leakage
    Reported lossNot disclosed