MetaMask / MetaMask/metamask-extension

Reset phishing warning triggers

Open
#32,832 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

external-contributor INVALID-ISSUE-TEMPLATE
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

### What is this about?

I've clicked on "enter site anyway" on a phishing warning. Now I want the warning for that site to trigger again when I re-enter it. There seems to be no way to reset phishing warnings, nor edit the blocklist.

How can I do this?

### Scenario

- Enter deceptive site;
- Get the "phishing page" trigger;
- Continue to it anyway;
- Close or refresh page;
- Enter same deceptive site;
- Site enters directly, but I want the warning to trigger again.

A button such as "reset all phishing site warnings" should be a no-brainer. Alternatively, a way to edit the current blocklist, or to edit the current list of whitelisted domains, should exist.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start by tracing the phishing-warning flow and the state used after choosing “enter site anyway”; define whether completion means a reset control, editable blocklist, or editable allowlist, then verify the reported scenario triggers the warning again.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.