What is the issue?
The contract
0x5151A19cD9919a7745a0E100f67f628058d5c27F
is appearing as
USDC
in user accounts.
Who is affected?
Users who may have interacted with USDC have the potential to have these fake phishing tokens appear in their transaction history.
What is the workaround?
Users can ignore the transactions, as there is currently no option to mark them as spam.
Keywords: incorrect token label, fake phishing, token misidentification