Browser Security

Use a separate browser profile for Web3

A malicious website or even an innocent website with a compromised supply chain can detect the presence of the Metamask plugin and trigger signing of messages/approvals. Using a separate browser profile to only access Web3-related content limits your attack surface to Web3 sites you visit instead.

Avoid installing plugins other than Metamask on your Web3 profile

Ad-blockers typically require access to the entire webpage across all URLs. While unlikely to happen, this means a compromised ad-blocker can potentially inject code that modifies functionality by the dApp you are accessing.