Leak -- Compromised POSTING key successfully protected



ā—ā—ā— šŸ’€ āš ļø šŸ’€ āš ļø ā—ā—ā—
It's a new day and another user leaked one of their private keys into the Hive Blockchain.

They COMPROMISED their...

private POSTING key

HOW: in a account-update2 operation


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: 25

  • Followers: 5

  • Account creation: 8/2017

  • Last social action on chain: 2017/8/25

  • Estimated account value: $ 0.85



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)


Keys-Defender features:

- Keys protection [live scan of transfers/posts/comments/other_ops. Warnings (reply and memo), auto-transfers to savings until fully restored, auto-reset of keys, ..] {see automatic posts on leak and monthly reports}
- Phishing protection [live scan of comments and posts to warn users against known phishing campaigns and compromised domains or accounts, scan of memos and auto-replies, anti phishing countermeasures - eg. fake credentials]
- Re-posting detection [mitigates the issue of re-posters]
- Code injection detection [live scan of blocks for malicious code targeting dapps of the Hive ecosystem]
- Anti abuse efforts [counteracts spam from hive haters and milking campaigns]


To support this project..
- Delegations:
10, 50, 100
500 HP, 1000 HP
Ā 
- Curation trail: Follow my curation trail on hive.vote to upvote all my posts with a fixed weight.



0
0
0.000
0 comments