Leak -- Compromised MEMO key successfully protected!!

in HiveDevs2 months ago (edited)


❗❗❗ 💀💀 ⚠️⚠️
It's a new day and another user leaked one of their private keys into the Hive Blockchain.

They COMPROMISED their...

private MEMO key

HOW: in a transfer operation published to the Hive blockchain.


The compromised account owner has now been notified in multiple ways. The identity of the user will be disclosed only in the monthly report in order to give them time to address the issue.



Compromised account stats:

  • Reputation: 55

  • Followers: 43

  • Account creation: May 2019

  • Last Post: 23 hours ago

  • Estimated account value: $ 14.46



Top 5 private ACTIVE keys protected:

1. @nextgen622: ~$ 28,000
2. @cryptoandcoffee:
~$ 8,400
3. @runridefly:
~$ 3,300
4. @globalmerchantio: ~$ 250

5. @j3dy: ~$ 120 (500 HIVE automatically protected for 9 days)


What does this bot do?

- Keys protection[live scan of transfers / posts / comments / other_ops. Auto-transfers to savings, auto-reset of keys, ..] {see automatic posts on leak and monthly reports}
- Phishing protection [live scan of blocks to warn against known phishing campaigns and compromised domains]
- Re-posting detection [mitigates the issue of re-posters]
- Code injections detection [live scan of blocks for malicious code targeting dapps of the Hive ecosystem]
- Anti spam efforts [counteracts spam from hive haters]


To support this bot..

                                       
- Delegation links:
10, 20, 30, 40 HP
50,100, 200 HP,
500 HP, 1000 HP
- Curation trail
Follow my curation trail on hive.vote to upvote all my posts with a fixed weight.

Sort:  

It's a shame that new users fall into this trap

well, it was just a bad copy and paste - his private key was sent in the transaction memo

hopefully no one takes advantage of it and that person is not harmed

They would only able to read his encrypted messages if the compromised account ever sent/received any.