🚨GoPlus Security Alert: A user just got drained for ~$550K USDC after signing a malicious #ncreaseAllowance# transaction. Victim: 0xa707d3D5d174f59d2C2b81491BDc5650E55F065B Phishing addresses: 0x9bcD8076840378a6eDFfc97ed824621C48D9104a 0x525dD9C729323FD842FCFeBd63659A4EE56444E1 0x6fE314fD4CF845f35fc461eD98e2FB8d9356B566 0x93b6B24DC6E6a1D5d72399e3A35498c4DbA1d6D1 0x98b2761559A348968C994D9856dCfc96B6f13C55 🛡 Stay safe—follow GoPlus’ four anti-phishing rules: 🚫 Don’t click unknown links 🚫 Don’t install unverified software 🚫 Don’t sign transactions you don’t fully understand 🚫 Don’t send funds to unverified addresses Install the GoPlus Security extension to block phishing links, risky signatures, malicious approvals, and suspicious transactions in real time 👇

For Approval transactions, HashPort verifies the Spender rather than the Token Because the object actually receiving the permission is the Spender or Operator When a user executes approve through a DApp, the wallet cannot only confirm that the Token is legitimate It also needs to confirm who the user is actually granting permission to This is where Approval Phishing becomes dangerous An attacker can copy a real DApp interface, use a real Token, and make the entire page look almost identical to the official website But once the user clicks Approve, the permission may actually be granted to the attackers Spender That is why HashPort defines the subject for approve increaseAllowance setApprovalForAll and permit related operations as the Spender or Operator The wallet needs to verify whether the current page is the official frontend associated with that Spender Because for an approval transaction, the object the user actually needs to trust is not the Token It is the address receiving the permission