Digital Asset
Intelligence
Security Incident · Exchange

EOSBET Fake Transfer Notification

·Historical incident record

Incident Overview

RAM was swallowed up by the malicious contract, and the game party failed to check the caller of transfer action, which led to the exchange of real token with fake token and "Transfer Error Prompt" vulnerability

Sources & References

Original incident referencehttps://www.jinse.com/lives/48517.htm (opens in a new tab)

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

    EOSBet

    Attack methodCode Vulnerability
    Reported loss42,000 EOS
  2. Incident date
    Target

    EOSBet

    Attack methodContract Vulnerability
    Reported lossNot disclosed
  3. Incident date
    Target

    EOSBet

    Attack methodTransfer error prompt
    Reported loss145,321 EOS
  4. Incident date
    Target

    Luckyos

    Attack methodRandom number attack
    Reported lossNot disclosed
  5. Incident date
    Target

    Fomo 3D

    Attack methodTransaction congestion attack
    Reported loss10,469.66 ETH