Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Numerous websites not present in blacklist are seeing the phishing warning #4332

Closed
adamkdean opened this issue Nov 2, 2020 · 2 comments · Fixed by #4335
Closed

Numerous websites not present in blacklist are seeing the phishing warning #4332

adamkdean opened this issue Nov 2, 2020 · 2 comments · Fixed by #4335
Labels
blocklist removal Issue or PR requesting removal of a domain from the blocklist

Comments

@adamkdean
Copy link

There are numerous reports now¹ reporting the phishing warning screen whose domains are not present (nor should be) in the blacklist. This is also happening for our domain edge.network, and yet there are no references to it in this repo.

Have any of the maintainers looked into this issue? Seems to me that the phishing detection is malfunctioning.

¹ #4317, #4323 #4322 #4291 #4287 #4247 (and more)

@409H
Copy link
Collaborator

409H commented Nov 2, 2020

Hi Adam, thanks for your ticket!

This was a collateral when we added ledger.com to our fuzzy list as there is a big phishing campaign against them right now. I have pushed your domains (and the ones you have highlighted) to the whitelist. Caches should update shortly.

You can also use this tool to see why a domain is blocked by MetaMask: https://metamask.github.io/eth-phishing-detect/

@409H 409H closed this as completed in #4335 Nov 2, 2020
@adamkdean
Copy link
Author

Thanks for your response, @409H, and for pushing the domains to the whitelist. Much appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocklist removal Issue or PR requesting removal of a domain from the blocklist
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants