eosblue.one

Memo attack

Estimated loss

—

VERDICT —UNRATED

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

▰ METHOD

Undisclosed

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

The attacker constructed the malicious memo, which caused the eosblue.one server parsing exceptions, thus continuously winning prizes or leading to unusually large refunds. Attack method (per SlowMist): Memo attack. Reported loss: 12,883 EOS.

Primary source

http://www.longkuicj.com/27528.html ↗

Sourced from

slowmist

Technical record