EOSBET

Fake Transfer Notification

Estimated loss

—

VERDICT —UNRATED

Verdict pending. Auto-ingested incidents are reviewed before a public verdict is rendered.

▰ METHOD

TOKEN SUPPLY

TOKEN-SUPPLYBYTECODE CATCHABLE →AI SCANNABLE →

Root cause

Root-cause analysis not yet published. The incident description below contains all currently available signal — review the attack transaction directly for definitive forensics.

Forensic narrative

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 Attack method (per SlowMist): Fake Transfer Notification. Reported loss: -.

Primary source

https://www.jinse.com/lives/48517.htm ↗

Sourced from

slowmist

Technical record