MetaMask / MetaMask/phishing-warning

Improve incorrectly flagged reporting flow

Open
#47 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
20
Forks
17
PR merge metrics
No merged PRs in 30d

Description

Now that our phishing warning page receives reports from multiple sources, we should ensure that users or site owners reporting a false positive can do it helpful.

One idea is to have pre-filled issues. I'm making an example here.

`https://github.com/MetaMask/phishing-warning/issues/new?body=domain:[$bad_flagged_url], source: [$name_of_the_list]`

We should provide all this information without affecting users' privacy while allowing them to open tickets in an open repo for human review.

This issue must be opened when the user clicks/tap the link [please report a detection problem].

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the phishing warning page entry point and locate the “please report a detection problem” link. Define done as providing a privacy-preserving report flow that includes the flagged domain and source when opening a review ticket, without exposing unnecessary user information.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.