cherry-pick: Fix Snaps usage of PhishingController #27833
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes two problems with Snaps usage of
PhishingController
. Following #25839 the PhishingController expects full URLs instead of hostnames as the input totestOrigin
. In that PR, the argument ofisOnPhishingList
was incorrectly changed. This PR also patches in some changes from thesnaps
repo that are currently blocked by a release: MetaMask/snaps#2835,MetaMask/snaps#2750
This PR cherry-picks a commit from
develop
that fixes this: 1f1e142Manual testing steps
eth-phishing-detect