RE: Introducing EOS911 Emergency - Prove ownership of a hacked EOS account on the genesis snapshot

You are viewing a single comment's thread from:

Introducing EOS911 Emergency - Prove ownership of a hacked EOS account on the genesis snapshot

in eos •  7 years ago  (edited)

Hey @eos42, thank you for taking the initiative to help people in the community.

I was a victim on the phishing attempt when block.one was hacked. I was emailing with the block.one developer team and one of their accounts responded back to me with a phishing site.

Since I trusted the block.one account and was having trouble finding the most legitimate way to register my EOS ERC20 tokens, there was no way for me to know it wasn't a scam.

This EOS community thread is about my case - https://www.reddit.com/r/eos/comments/8mfja0/please_help_scammed_by_developersblockone_email/

What can I do since I lost my tokens before the snapshot was taken? Who should I contact?

The stolen funds were not registered, so as far as the community is concerned these are totally burned tokens that rightfully belong to me.

If I need to prove that the original account belongs to me, please let me know and I can provide all the necessary information.

eos
7 years ago by

Downvoting a post can decrease pending rewards and make it less visible. Common reasons:

  • Disagreement on rewards
  • Fraud or plagiarism
  • Hate speech or trolling
  • Miscategorized content or spam

Submit
$0.00
    0
    Authors get paid when people like you upvote their post.
    If you enjoyed what you read here, create your account today and start earning FREE STEEM!