-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Labels
Sev2-normalNormal severity; minor loss of service or inconvenience.Normal severity; minor loss of service or inconvenience.needs-triageIssue needs to be triagedIssue needs to be triagedregression-prod-13.0.0Regression bug that was found in production in release 13.0.0Regression bug that was found in production in release 13.0.0team-confirmationsPush issues to confirmations teamPush issues to confirmations teamtype-bugSomething isn't workingSomething isn't working
Description
Describe the bug
The 'first time interacting with' warning only displays when sending ETH - not UDSC (or any ERC20s) - from the native send flow. This alert is important to have consistency on in order to prevent malicious transactions. Presumably, this is because it is an ERC20 and we are not checking the recipient address of the transfer function.
Expected behavior
I expect to see the 'first time interacting with' warning in the simple send flow for both native assets and ERC20s.
For clarity: on ERC20s I expect to see the warning not based on my interaction history on USDC's contract itself, but rather the recipient of the transfer function.
Screenshots/Recordings
Steps to reproduce
- Navigate to the Send flow from the Home page of MetaMask Extension
- Select an ERC20 asset and set the 'to' address as an address you haven't interacted with before (e.g - vitalik.eth
0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045
) - No warning exists (bug)
Error messages or log output
Detection stage
In production (default)
Version
13.0.0
Build type
None
Browser
Chrome
Operating system
MacOS
Hardware wallet
No response
Additional context
No response
Severity
No response
Metadata
Metadata
Assignees
Labels
Sev2-normalNormal severity; minor loss of service or inconvenience.Normal severity; minor loss of service or inconvenience.needs-triageIssue needs to be triagedIssue needs to be triagedregression-prod-13.0.0Regression bug that was found in production in release 13.0.0Regression bug that was found in production in release 13.0.0team-confirmationsPush issues to confirmations teamPush issues to confirmations teamtype-bugSomething isn't workingSomething isn't working
Type
Projects
Status
To be triaged