Is MetaMask – Crypto Wallet safe?
MetaMask sends transaction details to its Blockaid security-alerts API by default to check for threats before signing.
When a user initiates a transaction or signing request, MetaMask transmits the full JSON-RPC request body — including wallet address, recipient, value, and calldata — to security-alerts.api.cx.metamask.io for threat validation. This is the Blockaid phishing/drainer detection feature and is active by default. A local WASM model is used as a fallback only if the remote API is unavailable.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
What it can do
Permissions this extension asks for, as declared in version 13.53.0.0. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on every site you visit
http://*/* and 2 more
Read and change your data on every secure site you visit
https://*/*
Read and change your data on eth
*://*.eth/
Store data in your browser
storage
Store an unlimited amount of data in your browser
unlimitedStorage
Act on the current tab, but only after you click the extension
activeTab
Watch every request your browser makes
webRequest
Watch, block and rewrite every request your browser makes
webRequestBlocking
Show you desktop notifications
notifications
Sign you in with your Google account
identity
Read and change cookies, including the ones that keep you signed in
cookies
Where it sends data
Destinations our analysis observed MetaMask – Crypto Wallet contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- security-alerts.api.cx.metamask.io
MetaMask – Crypto Wallet sends data to security-alerts.api.cx.metamask.io. No other extension we have analyzed sends data here.