Malicious token impersonating Tether (USDT) — request to blocklist

Open Beginner friendly
#1,911 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
blockchain, javascript
Domain
blockchain, security

Research direction

Start by inspecting the contract-address mappings in the MetaMask/contract-metadata repository and look for existing blocklist or removal entries. Search for TTWTMq3jRedLJ8paJLCKvFTgkteSNdSiEy and confirm the metadata no longer presents it as Tether or a legitimate asset. Done means the impersonating Tron token is blocked or removed from the affected metadata.

Written by the indexing model from the issue text.

Description

This token is impersonating the official Tether (USDT) stablecoin and is currently displaying with a Tether logo and price in MetaMask, misleading users.

Contract address: TTWTMq3jRedLJ8paJLCKvFTgkteSNdSiEy
Network: Tron (TRC-20)
Fake project name: TetherAsset / QSDT
Fake website: tetherasset.com — the site's own footer admits in small print: "Transfer Receipt and QSDT are independent digital assets developed within the TetherAsset ecosystem. They are not issued by, sponsored, endorsed by or affiliated with Tether Limited, Tether Holdings Limited or USDT" — confirming this is a deliberate impersonation of the real Tether brand, not an unrelated project that happens to share a name.

Fake X/Twitter account: x.com/TetherAsset (registered Nov 2025, uses Tether's logo and color scheme)
GeckoTerminal pool: labeled "USDT/Tether" (Sunswap V3, Tron network)
Logo appears to be sourced via a fork of trustwallet/assets: github.com/tetherasset

Official Tether reference for comparison: tether.to, @Tether_to on X.

Requesting this contract be added to the blocklist / removed from any metadata that displays it as a legitimate Tether-branded asset.

Dominant language
JavaScript
Stars
585
Forks
1.4k
Avg merge
2d 8h
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MetaMask/contract-metadata

All issues in MetaMask/contract-metadata

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.