MetaMask Wallet Extension: MEV Frontrunning and Sandwich Attacks—Why Your Swap Prices Change Before Confirmation

A user approves a swap on Uniswap through their MetaMask wallet extension, sees a quoted price of 1 ETH for 1,500 USDC, and submits the transaction. Within seconds, the price moves to 1 ETH for 1,480 USDC. The transaction still settles, but the user receives less than expected. This is not price volatility in the traditional sense. It is a structural consequence of how Ethereum and other EVM networks process transactions: a public mempool, ordered auction, and the opportunity for sophisticated actors to intercept and profit from user intent before it executes. Understanding how this happens, what MetaMask shows and does not show, and how to protect yourself requires looking beyond the wallet interface into the mechanics of maximal extractable value.

MetaMask, available as a browser extension, mobile app, and web interface, remains one of the most widely used self-custodial wallets for interacting with Ethereum and EVM networks. It handles private key management locally, displays transaction details, and communicates with blockchain networks through RPC endpoints that the user selects or that MetaMask provides by default. Despite its familiarity and convenience, the wallet’s interface can present an incomplete picture of what actually happens between the moment a user clicks “confirm” and the moment their transaction is included in a block. The quoted price, displayed gas estimate, and final settlement can differ significantly—not because of user error, but because of how fees, ordering, and extraction mechanisms work on public blockchains.

How the public mempool exposes your transaction intent

When you initiate a swap through a decentralized exchange and use your MetaMask wallet extension to sign the transaction, your intent enters a network of thousands of nodes before being included in a block. This period—often measured in seconds—is critical. Your transaction sits in the mempool, publicly visible to anyone running a full node, with the exact asset amounts, receiving address, slippage tolerance, and wallet address attached. This transparency is fundamental to how blockchains work: everyone can verify the state and incoming transactions. But transparency also means exposure.

Unlike traditional finance, where orders are submitted to a centralized order book and matching happens inside a protected system, Ethereum and other EVM networks make your orders visible before execution. Miners and validators can see your transaction and decide whether to include it, delay it, or position other transactions around it. Searchers—sophisticated participants running custom software—monitor the mempool specifically to identify profitable opportunities. A large token swap, a liquidation, an NFT purchase, or an arbitrage opportunity become visible to the entire network simultaneously. Your MetaMask wallet extension sends the transaction; the mempool broadcasts it.

The quoted price in MetaMask is a snapshot from the moment you initiated the transaction. It reflects the state of the liquidity pool at that instant. But between the moment you see that price and the moment your transaction actually executes—potentially seconds or even minutes later, depending on network congestion and gas price competition—the pool state can change. Other transactions may execute first, shifting the reserves in that liquidity pool. A searcher may intentionally place a transaction before yours, move the price, and then place another transaction to profit from the expected change your transaction will cause.

Maximal extractable value and sandwich attacks explained

Maximal extractable value, commonly abbreviated as MEV, refers to the profit that can be extracted from blockchain transaction ordering and execution beyond the standard transaction fees. It was previously called “miner extracted value” before proof-of-stake, but the principle remains: anyone with the power to order or reorder transactions can capture value from that power. For a user making a swap through MetaMask, the most direct form of MEV exploitation is a sandwich attack.

A sandwich attack operates in three steps. First, a searcher monitors the mempool and identifies a pending transaction—your swap, let us say, for 10 ETH into USDC on a liquidity pool. The searcher knows the transaction size is large enough to shift prices and predicts the direction and magnitude of that shift. Second, the searcher places their own transaction before yours, buying USDC just before your larger purchase hits the pool. This front-running transaction executes first, moving the price upward slightly. Third, your transaction executes immediately after at the worse price, and then the searcher sells the USDC they bought back at the now-higher price, locking in the difference as profit.

The loss falls entirely on you. Your MetaMask wallet extension showed you a price of 1 ETH for 1,500 USDC, but by the time your transaction executes, the pool state has changed due to the front-running transaction. You receive only 1,480 USDC instead. The searcher has captured approximately 20 USDC of MEV—the value extracted from reordering. This happens on every EVM network where transaction ordering is transparent, including Ethereum Layer 1, Arbitrum, Optimism, Polygon, and others. It is not a security failure or a bug. It is a structural feature of transparent, public mempools combined with the ability to order transactions.

Sandwich attacks are profitable enough that they are automated. MEV bots run continuously, scanning every pending swap, bridge transfer, and protocol interaction. The MEV extracted from Ethereum across one year has historically exceeded hundreds of millions of dollars. Individual users rarely see a dramatic loss on a single swap, but the losses compound, especially for those executing large trades or operating on congested networks.

What MetaMask shows and what it hides in transaction details

When you open your MetaMask wallet extension to approve a transaction, the interface displays several fields: the asset being sent, the asset being received, the estimated amount you will receive, the gas fee, the total cost, and the network. These details matter, but they represent an incomplete view of the actual cost of your transaction. The quoted received amount is calculated based on current liquidity pool state. The gas fee estimate is based on current network conditions. Both can shift after you sign.

The MetaMask wallet extension shows the gas fee in gwei or your local currency, and it offers options to set the priority: standard, fast, or custom. Higher gas prices increase the likelihood of quicker inclusion, which theoretically reduces the window for MEV exploitation. But gas price alone does not prevent MEV. Even a transaction with the highest possible gas priority can still be sandwiched, because the front-runner can pay a higher gas price than you, secure a position ahead of your transaction, and execute their sandwich before your transaction includes. Gas priority is an auction, and MEV searchers have unlimited capital to outbid.

The MetaMask wallet extension does not clearly display slippage—the acceptable percentage difference between the quoted price and the actual executed price. Slippage tolerance is typically set in the dapp itself, not in MetaMask. It acts as a safety valve: if the price moves more than the slippage tolerance during execution, the transaction reverts and fails. A 0.5% slippage tolerance means the transaction will only execute if you receive at least 99.5% of the quoted amount. But MetaMask itself does not make this threshold obvious to users reviewing the transaction before signing. The wallet shows the quoted output; it does not prominently display what range of actual outputs is acceptable or what will happen if the execution price falls outside that range.

Why gas fees do not protect you from MEV

A common misconception is that paying higher gas fees, using the MetaMask wallet extension’s “fast” or “instant” settings, reduces MEV exposure. In practice, gas fees and MEV are separate cost dimensions. Gas is the fee paid to the network for executing code. MEV is value extracted from transaction ordering. A transaction with extremely high gas priority can still be sandwiched if the searcher is willing to pay an even higher gas fee to position their front-running transaction ahead of yours.

MEV searchers operate with sophisticated tools and significant capital. They use custom RPC endpoints, direct relay connections to builders and validators, and flash loans to fund their positions without risking their own capital. They bid far higher gas fees than ordinary users would consider acceptable because they are capturing tens or hundreds of thousands of dollars in MEV. Your MetaMask wallet extension’s “fast” setting might use 100 gwei; the searcher can use 500 gwei and still profit. The user’s gas fee is a rounding error compared to the MEV at stake.

The real protection against MEV comes not from paying more for gas, but from reducing the size of the opportunity and the duration of exposure. Smaller transactions create less price movement and less profit incentive for searchers. Shorter confirmation times reduce the window in which a searcher can act, though on congested networks this window may extend beyond the user’s control. On Layer 2 networks like Arbitrum or Optimism, block times are faster and MEV opportunities are smaller because price impact from smaller amounts of liquidity is different. The most direct protection, however, is slippage tolerance and the awareness that the quoted price in your MetaMask wallet extension is historical—a reflection of conditions that existed when you initiated the transaction, not when it will execute.

Slippage tolerance and why MetaMask does not enforce it

Slippage tolerance is the user’s primary defense against both MEV and ordinary price volatility. Setting it correctly requires understanding your acceptable loss and the typical price movement on that network and pair. A slippage tolerance of 0.1% is protective but may cause transactions to fail on congested networks during volatile conditions. A tolerance of 5% is more forgiving but exposes the user to larger losses from MEV.

The MetaMask wallet extension does not set slippage tolerance itself. That setting lives in the decentralized exchange interface—Uniswap, 1inch, Curve, or whichever platform you use. MetaMask acts as the transaction conduit: it presents what the dapp is asking you to sign, encrypts it with your private key, and broadcasts it to the network. The slippage setting is buried in the dapp’s UI, often in an “advanced settings” or “swap settings” menu. Users who do not consciously set it may accept whatever default the dapp provides, which is sometimes permissive enough to allow substantial MEV losses.

When slippage tolerance is exceeded, the transaction reverts. The user’s assets are not sent; the dapp contract cancels the swap and returns the funds. This safety mechanism costs gas—the failed transaction still consumes resources to execute and revert. But failed execution is preferable to executing at a catastrophically bad price. Understanding this trade-off is crucial. Your MetaMask wallet extension will not warn you if slippage tolerance is too high; that judgment falls to you.

Blockchain networks, RPC endpoints, and the nodes MetaMask connects to

MetaMask communicates with blockchain networks through RPC endpoints. You can use the default endpoints that MetaMask provides, or you can configure custom endpoints to connect to your own node, a third-party node provider, or a node relay service. The choice of endpoint affects which version of the mempool you see and potentially which transactions other participants see. If you are connecting through a node operated by Infura or Alchemy, MetaMask is sending your transactions through their infrastructure. These providers are reputable, but they also have visibility into the transactions you are signing.

Alternative RPC options include MEV-protecting services that strip transaction details, apply ordering guarantees, or use encrypted mempools to reduce the visibility of user intent before execution. Services like MEV-Blocker and Flashbots Protect attempt to keep your pending transaction hidden from searchers by removing it from the public mempool and routing it through a private relay. However, MetaMask’s default configuration does not use these protections. A user must actively configure MEV-protecting RPC endpoints within the MetaMask wallet extension settings to benefit from them.

The RPC endpoint you select also determines the speed and reliability of price quotes and transaction confirmation. Public endpoints may be rate-limited. Third-party endpoints may have latency that causes the quoted price in your MetaMask wallet extension to become stale. The decentralized exchange interface you use may query its own RPC nodes rather than the one MetaMask displays, creating mismatches between the price MetaMask shows and the price the dapp actually executes at. These are operational challenges separate from MEV, but they compound the uncertainty around what your transaction will ultimately cost.

Practical strategies to reduce MEV exposure when using MetaMask

The most direct defense is slippage tolerance. Before executing any swap through your MetaMask wallet extension, verify the slippage setting in the dapp interface. Check the “settings” or “advanced options” menu. Set slippage tolerance to the lowest value you are comfortable with—for stable pairs, 0.05% or 0.1% is reasonable; for volatile pairs, 0.5% to 1% may be necessary. Understand that if slippage is exceeded, the transaction fails and you keep your original assets but lose the gas fee.

Second, break large transactions into smaller pieces if practical. A single swap of 100 ETH is far more attractive to MEV searchers than ten swaps of 10 ETH each. Smaller transactions create less price impact and less extraction opportunity. This strategy increases total gas costs—you pay for multiple transactions instead of one—but for large positions, the MEV saved can exceed the additional gas.

Third, consider the timing of your transaction. Executing swaps during periods of lower congestion, when the network is less busy and competition for block space is lower, can reduce the number of pending transactions in the mempool and thus reduce MEV opportunity. Monitor network conditions through tools like the Ethereum gas tracker or equivalent Layer 2 dashboards. Avoid executing large trades during network spikes or major announcements.

Fourth, if you want to minimize exposure further, configure MetaMask to use an MEV-protecting RPC endpoint. Services like MEV-Blocker provide RPC endpoints that route transactions through private relays and encrypted mempools. When you submit a transaction through these endpoints via your MetaMask wallet extension, it is not broadcast to the public mempool. Instead, it is sent directly to a private pool where builders and validators can include it, but searchers cannot see it in advance. This does not eliminate MEV entirely—builders can still extract some value through transaction reordering—but it removes the opportunity for public mempool surveillance and front-running.

Finally, understand the limitations of your DeFi wallet. MetaMask is a tool for managing credentials and signing transactions. It is not responsible for MEV prevention; that responsibility falls partly on you through slippage settings, and partly on the dapp and the RPC endpoint you use. When evaluating whether to use MetaMask, whether to metamask wallet extension for a particular transaction, and how to configure it, remember that MetaMask’s interface shows you a quote that may become outdated within seconds. The security and efficiency of your swap depend on the full chain: wallet, RPC endpoint, dapp, slippage tolerance, transaction size, and network conditions.

MEV on different EVM networks and the scaling trade-off

Ethereum Layer 1 has historically experienced the highest MEV absolute value, measured in dollars extracted per day, because it handles the largest volume and has the most liquid markets. Layer 2 networks like Arbitrum and Optimism have lower MEV in absolute terms because they have less volume, but the percentage cost as a share of transaction value can be similar or even higher on smaller pairs. A USDC-to-stablecoin swap on Optimism might experience 0.1% slippage from MEV; the same swap on Ethereum might experience 0.05% because there is more liquidity and less price impact.

Transaction finality also varies. Ethereum finalizes blocks every 12 seconds on average, but MEV exposure can extend longer if network congestion causes your transaction to remain in the mempool for minutes. Optimism and Arbitrum finalize faster in relative terms, reducing the mempool exposure window. However, they use different sequencing models. Arbitrum uses a centralized sequencer, which theoretically reduces MEV by controlling transaction order, but introduces centralization risk. Optimism is moving toward decentralized sequencing. Neither eliminates MEV; they redistribute how and when it can be extracted.

When choosing which network to use for a swap, consider not only the gas fees displayed in your MetaMask wallet extension, but also the MEV environment. A network with 1 gwei gas but 0.5% MEV loss may be more expensive than a network with 5 gwei gas and 0.1% MEV loss, especially on large trades. The choice depends on your transaction size, the liquidity of the pair, and the network’s current congestion. MetaMask lets you switch networks easily; understanding the full cost landscape requires looking beyond the wallet interface.