Digital Asset
Intelligence
Theme

Search 3CBlock

News, exchanges, regulatory intelligence, reviews and Voices.

Security Incident

ToBet Roll back attack

Historical incident record

Incident Overview

The attacker rolls back the transaction when placing a bet. From the time the bet is placed until the transaction is rolled back, the betting data will temporarily exist in the database of the current node; and Tobet queries the betting by polling the node database outside the contract. The lottery will be drawn outside the contract and the result will be passed to the lottery action; when the attacker keeps betting and rolls back the transaction, because the betting and Tobet polling use the same node, the Tobet lottery polling can query the database betting information for a short time and draw the lottery. . However, the attacker's bet was not successful, and the contract would continue to draw prizes for him, resulting in no capital arbitrage.

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

    MORE Markets

    Attack methodSmart Contract Vulnerability
    Reported loss$ 308000
  2. Incident date
    Target

    Lighter

    Attack methodAPI key leakage
    Reported loss$ 10,393,057
  3. Incident date
    Target

    Chain Games

    Attack methodSmart Contract Vulnerability
    Reported loss$ 20,000
  4. Incident date
    Target

    HyprEarn

    Attack methodNot disclosed
    Reported lossNot disclosed
  5. Incident date
    Target

    Kava Lend

    Attack methodSmart Contract Vulnerability
    Reported loss$ 3,760,000
  6. Incident date
    Target

    EOS Max

    Attack methodRoll back attack
    Reported loss55,526 EOS
  7. Incident date
    Target

    TRUSTBET

    Attack methodReplay attack
    Reported loss11,501 EOS