New Security Threats to Web3.0 Mobile Wallets: Modal Window Phishing Attacks

Recently, security researchers have discovered a new type of phishing technique targeting Web3.0 mobile Wallets, known as "modal phishing attacks." This attack primarily exploits the modal windows in mobile Wallet applications to mislead users, thereby tricking them into approving malicious transactions.

The Principle of Modal Phishing Attacks

Modal phishing attacks primarily target user interface elements in Web3.0 cryptocurrency Wallets, particularly modal windows. Attackers can manipulate the information displayed in these windows to make it appear as if it comes from legitimate decentralized applications (DApp), thereby deceiving users into approving transactions.

The reason this type of attack is effective is that many wallet applications fail to fully verify the legitimacy of the information presented. For example, some wallets directly trust metadata from external SDKs without conducting additional verification.

Attack Cases

1. Wallet Connect phishing: Attackers can control information such as the name, icon, and website address of the DApp, making phishing sites appear to be legitimate DApps. When users connect their wallets via Wallet Connect, this false information will be displayed in the modal window of the wallet.

2. Smart Contract Information Phishing: Certain wallets (such as MetaMask) display the function names of smart contracts in a modal window. Attackers can create malicious contracts with misleading names, for example naming the transfer function "SecurityUpdate" to deceive users into approving the transaction.

Prevention Suggestions

1. Wallet Developer:
   • Always treat externally provided data as untrusted.
   • Carefully select the information displayed to users and verify its legality.
   • Consider filtering keywords that may be used for phishing attacks.

2. User:
   • Remain vigilant for every unknown transaction request.
   • Carefully check the transaction details and do not approve the transaction based solely on the information displayed in the modal window.
   • Use official channels to download and update the Wallet application.

3. Protocol Developer:
   • Consider adding verification mechanisms at the protocol level, such as Wallet Connect, which can verify the validity of DApp information in advance.

With the development of Web3.0 technology, these new types of security threats are also continuously evolving. Both users and developers need to enhance their security awareness and work together to maintain the safety of the Web3.0 ecosystem.