You are viewing a single comment's thread from:

RE: Phishing on Hive? No more. Solution for all Frontends.

in HiveDevs • 3 years ago

That looks pretty cool!
Every measure that can reduce the chance of people falling victim to a phishing attack should be considered.

Any known phishing link in the UI will be red and strikethrough-ed.
So, is it using a database of known phishing links? The only pitfall would be that people immediately trust links that are not in this database yet and therefor not striked-through.
But then again you will save a lot of peoples keys too.

Posted Using LeoFinance Beta

3 years ago in HiveDevs by
$0.24
  • Past Payouts $0.24
  • - Author $0.12
  • - Curators $0.12
1 vote
Reply 2
Sort:  
  • Trending
    • [-]
     3 years ago (edited) 

    Yes it is using @spaminator’s list of known phishing domains: https://spaminator.me/api/p/domains.json

    Every time a new phishing wave starts, the attacker’s domain gets added there by the @spaminator team.

    Maybe you’re right. That’s also why I was thinking that we should automate the addition of new entries to the blacklist. What I had in mind for this was:

    • If a top 20 witness sends a memo like “phish:justinscam.com” the reported domain gets automatically added to the blacklist;
    • Same if at least 2 witnesses in position between 40 and 20 send a memo in that format.
    I could even host myself a copy of @spaminator's blacklist and start offering this automation mechanism in @keys-defender..
    🤔💡 - PS. DONE
    [-]
     3 years ago  

    Seems like a good plan!

    Posted Using LeoFinance Beta

    $0.00
      Reply