Millions of people trust MetaMask’s built-in swap feature every week without a second thought. What almost none of them know is that one of the contracts powering it has been sitting on Tether’s blacklist since 2021, quietly unable to move its own USDT for nearly five years.
The discovery came from blockchain security researcher Specter, who was cross-referencing contract addresses against blacklist records and noticed something odd: a contract tagged “Metamask: Swap Router” on Etherscan came back flagged. Not flagged recently. Flagged in 2021, and never removed. When I dug into it myself, the details held up exactly as described, verifiable on-chain, no exaggeration needed.
A Contract Users Trust Has Been Flagged Since 2021
What makes this genuinely strange is that this isn’t some obscure, abandoned contract. It’s part of the swap infrastructure behind one of the most widely used self-custody wallets in crypto. MetaMask Swaps, the in-app token aggregator that routes trades across multiple decentralized exchanges, launched on desktop in October 2020 and expanded to mobile the following spring, right around the window when this specific router contract would have gone into active use. Somewhere in that early period, Tether’s compliance system added it to the blacklist, and it has stayed there ever since, unnoticed until now.
The Exact Address Tether Blacklisted
The contract in question is labeled directly on-chain as “Metamask: Swap Router,” sitting at address 0x881D40237659C251811CEC9c364ef91dC08D300C on Ethereum. You can pull up the full contract record on Etherscan and see it for yourself — verified source code, a live transaction count north of 17 million, and a current balance spread across more than a dozen chains. It’s not a dead contract. It’s actively processing swaps right now, for real users, while sitting on a blacklist most of them will never check.
How Tether’s Blacklist Actually Works
Tether’s USDT contract has carried a built-in blacklist mechanism since its early Ethereum deployment, a BlackList module that lets Tether’s contract owner call addBlackList on any address, after which that address is permanently barred from sending USDT out through the standard transfer function. It can still receive USDT. It just can’t move it back out. Tether doesn’t publish a public explanation for individual blacklist entries, and this case is no exception, there’s no official statement tying this specific flag to a specific incident. What’s verifiable is the mechanism itself and the current state of the flag, both of which anyone can confirm directly by querying the USDT contract’s isBlackListed function on Etherscan, entering the router’s address, and reading the result straight from the chain.
I did exactly that while writing this, mostly out of disbelief that a contract this central to MetaMask’s swap flow could be sitting on a stablecoin issuer’s blacklist without anyone catching it publicly for five years. The function returns exactly what Specter described.
Why Nobody Noticed For Nearly Five Years
Part of the answer is mundane: a blacklisted address can still receive tokens, and most swap flows involving this router never require it to hold and forward USDT for long enough to hit the restriction in a way that breaks the user’s experience. Swaps typically route through in a single atomic transaction, and plenty of trading pairs never touch USDT at all. The flag sits there, technically active, mostly invisible, because the specific failure condition it creates doesn’t come up often enough to trigger obvious complaints. It took someone deliberately cross-referencing contract addresses against blacklist records to surface it at all.
What A Blacklisted Router Means For Everyday Swaps
Here’s where it gets tangible rather than theoretical. Etherscan’s own token holdings for this contract currently show a nonzero USDT balance sitting inside it, a few thousand dollars’ worth, alongside a longer list of other tokens the router is holding. Because the contract can’t send USDT out once received, any USDT that ends up parked there through a swap that didn’t complete cleanly has nowhere to go. It’s not stolen. It’s not lost in the traditional sense. It’s just permanently stuck, the same category of dead-end that any blacklisted wallet produces, except this one belongs to infrastructure millions of people route trades through without knowing its status.
For the vast majority of MetaMask Swaps users, this changes nothing day to day, most swaps complete fine, and the blacklist only bites in the specific case where USDT gets stranded mid-route. But it’s a reminder that “widely used” and “actively audited for compliance status” aren’t the same thing. A contract can process 17 million transactions and still be carrying a five-year-old flag nobody thought to check.
Checking The Flag Yourself, On Chain
None of this requires taking anyone’s word for it. The router’s contract page is public on Etherscan, and the blacklist status is a single read-function call away on Tether’s own USDT contract, both linked above, both verifiable in under a minute. That’s the part I keep coming back to: this wasn’t hidden. It was sitting in plain sight on-chain the entire time, in a place nobody thought to look until Specter’s cross-check surfaced it. Whether Tether ever reviews or lifts the flag is an open question but the flag itself, and how long it’s been there, isn’t in dispute. It’s on the chain for anyone to check.
Disclosure: This is not trading or investment advice. Always do your research before buying any cryptocurrency or investing in any services. Follow us on X @nulltxnews
Be the first to comment