MetaMask / MetaMask/metamask-extension
Create system to block/revoke malicious RPCs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
As a user in a layer 2 ecosystem that doesn't want to get phished,
If I add a malicious RPC url, and it gets reported, I'd like it to get automatically removed, and I'd like to receive a notice explaining what happened!
Acceptance criteria:
- MetaMask team should maintain a list of known malicious RPC URLs (like on MetaMask/eth-phishing-detect).
- MetaMask clients should periodically check that list
- If a MetaMask client finds one of its custom RPCs is listed, it should deactivate it immediately.
- A notice explaining the removal should be provided to the user on their next interaction with MetaMask.
- The user should have the option to disable this warning for that RPC.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how MetaMask stores and manages custom RPC URLs, then review the referenced MetaMask/eth-phishing-detect list and existing client update mechanisms. Done means malicious custom RPCs are periodically identified and deactivated, with a user notice and an option to disable that warning for the affected RPC.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100