Digital Asset
Intelligence
Theme

Search 3CBlock

News, exchanges, regulatory intelligence, reviews and Voices.

Security Incident · Exchange

Dexible Contract Vulnerability: $2M Reported Loss

Historical incident record

Incident Overview

The DEX tool Dexible was suspected of being attacked and lost about $2 million. According to the analysis, there is a logical loophole in the selfSwap function of the Dexible contract, which will call the fill function. This function has a call to the attacker's custom data, and the attacker constructs a transferfrom function in this data, and transfers other users (0x58f5f0684c381fcfc203d77b2bba468ebb29b098) address and its own attack address (0x684083f312ac50f538cc4b634d85a2feafaab77a), causing the tokens authorized by the user to the contract to be transferred by the attacker.

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

    LaunchZone

    Attack methodContract Vulnerability
    Reported loss$ 700,000
  2. Incident date
    Target

    Orion Protocol

    Attack methodReentrancy Attack
    Reported loss$ 3,000,000
  3. Incident date
    Target

    SUCKR

    Attack methodRug Pull
    Reported lossNot disclosed
  4. Incident date
    Target

    Balancer

    Attack methodAffected by Euler Finance Attack
    Reported loss$ 11,900,000
  5. Incident date
    Target

    Yield Protocol

    Attack methodAffected by Euler Finance Attack
    Reported loss$ 1,500,000
  6. Incident date
    Target

    Block Tower Capital

    Attack methodAffected by Dexible events
    Reported loss$ 1,500,000
  7. Incident date
    Target

    Platypus

    Attack methodFlash Loan Attack
    Reported loss$ 9,000,000