MetaMask has introduced a new safeguard designed to close a dangerous gap in how crypto wallets confirm what a transaction actually does. The feature, called Added Protection, enforces a strict match between the outcome shown in a transaction preview and what actually happens on-chain. If the two fail to line up, the transaction is stopped automatically before it can cause damage.

As reported by The Cryptonomist, the update targets one of the oldest tricks in the crypto scam playbook: showing the user a harmless-looking preview while the underlying transaction does something entirely different — draining funds or approving malicious contract access, for example.

From Passive Previews to Active Verification

Added Protection operates on a simple but powerful principle: whatever a wallet displays before signing must match what actually happens once the transaction settles on-chain. Every Ethereum or EVM transaction processed through a wallet with the feature enabled has to produce a result identical to the one that was previewed beforehand.

This represents a meaningful shift in how MetaMask's transaction security is enforced at the protocol level, moving from passive display to active verification. Users are no longer relying solely on a static preview screen; the wallet now checks whether the on-chain execution matches expectations before finalizing anything.

Mismatched Transactions Fail Automatically

When a mismatch occurs, the transaction does not go through. Instead, it fails automatically, and the only cost to the user is the gas fee already spent on the attempt. In practice, this caps the financial downside of a manipulated transaction: no funds are moved, no permissions are granted, and no assets change hands beyond the gas that was paid.

That marks a notable improvement over previous wallet behavior, in which a deceptive transaction could execute in full and result in a total loss of funds rather than a small fee.

Rollout and Network Coverage

Enabled by Default in Extension Version 13.45

Added Protection is already live and switched on for most users rather than sitting behind an opt-in toggle. MetaMask enabled it by default starting with extension version 13.45, so anyone running that version or later receives the protection automatically, with no settings changes required.

Because the safeguard ships as a default setting rather than an optional feature, adoption is immediate across the user base running the updated extension. That lowers the chance that vulnerable or less security-conscious users skip the protection simply because they never knew it existed. For users still on earlier versions, the protection arrives only once the extension is updated.

Coverage Spans 13 EVM Networks With EIP-7702 Smart Accounts

The feature currently covers 13 EVM networks that support EIP-7702 smart accounts, an Ethereum standard that expands how accounts can execute and batch transactions. Tying Added Protection to EIP-7702 specifically suggests MetaMask is prioritizing the networks where this newer account model is already active, since that is where the outcome-versus-preview verification can be most reliably enforced.

That coverage also has a defined edge for now: transactions on networks or account setups outside those 13 EVM networks do not fall under this preview-versus-execution check, making the feature's footprint a practical detail for wallet holders to confirm against their own setup.

Built to Blunt Red Pill Attacks

MetaMask says Added Protection is designed specifically to guard against Red Pill attacks — a category of exploit aimed at tricking a wallet's transaction preview into displaying one outcome while a different, harmful action actually executes. By requiring the real result to match the preview exactly, the feature is intended to neutralize the gap between what users see and what happens on-chain, closing off a manipulation vector that has made Red Pill attacks on Ethereum and other EVM chains particularly hard to catch before it is too late.

The change matters for everyday wallet holders because transaction previews have long been treated as trustworthy by default. If a preview can be spoofed while the underlying transaction does something else entirely, users have had no reliable way to know they were about to be scammed until the damage was already done. Added Protection removes that blind trust by inserting a verification check between the preview and the final execution.

Frequently Asked Questions

What is MetaMask's Added Protection feature?

Added Protection is a security feature that requires Ethereum or EVM transaction outcomes to match their previews, automatically failing a transaction if the two differ.

What happens if a transaction outcome differs from its preview?

The transaction fails automatically, and the user loses only the gas fee spent on the attempt.

Which networks support MetaMask's Added Protection?

The feature supports 13 EVM networks that implement EIP-7702 smart accounts.

Is Added Protection enabled by default?

Yes, it is enabled by default starting with MetaMask extension version 13.45.