Crime intelligence

Crypto phishing domain lists

ScamSniffer and MetaMask each publish a blocklist of crypto phishing and wallet-drainer websites. CompliAPI ingests both daily and checks them on every website screen, flagging a hit as crime intelligence, distinct from any sanctions designation.

Publisher
ScamSniffer and MetaMask
List type
Crime intelligence
Refresh
Ingested daily (ScamSniffer's public file runs 7 days behind its detections)
API list slugs
scamsniffermetamask_phishing
Official source
ScamSniffer scam-database and MetaMask eth-phishing-detect (GitHub)
License
ScamSniffer scam-database: GPL-3.0. MetaMask eth-phishing-detect: DBAD 1.2. Neither list is republished here.
Download
Not republished here: the lists' licences do not allow it. Take the full lists from their publishers.

About this list

Two community blocklists track the websites used to steal crypto: fake exchange and wallet sites, airdrop-claim pages and wallet drainers. ScamSniffer publishes its scam database on GitHub, and MetaMask maintains eth-phishing-detect, the list behind the phishing warning in its wallet. Between them they name hundreds of thousands of hosts and change every day.

This is crime intelligence, not a government list: a site is here because its publisher judged it to be phishing, not because an authority designated it. A match sets flagged: true with list_type "crime" and never sets sanctioned. Absence from the lists is not evidence that a site is safe.

These lists work differently from the others on this site. They are checked by the website screening endpoint only: they are left out of the free search and the delisting feed, and CompliAPI does not republish them, because their licences (GPL-3.0 for ScamSniffer, DBAD for MetaMask) do not allow it. The full lists are available from their publishers at github.com/scamsniffer/scam-database and github.com/MetaMask/eth-phishing-detect.

What CompliAPI extracts

  • Phishing and wallet-drainer website hosts
  • Single phishing pages on shared hosting platforms

How CompliAPI handles it

  1. Daily ingestion of both files

    CompliAPI pulls both published files once a day. ScamSniffer releases its public file with a 7-day delay, so a domain it detected this week is not in the list yet. Entries on MetaMask's own allowlist are skipped.

  2. Exact host matching

    A listed host matches when the website you screen has the same host: the scheme, a leading www., the port, the path and the query string are ignored. Subdomains are separate hosts, so a listed evil.example does not match app.evil.example.

  3. Shared platforms are matched by page

    Phishing pages hosted on a shared platform, such as a Google Sites page, are listed with their path and match only that page. The platform's own host is never listed, so screening it stays clean.

  4. Flagged, never sanctioned

    Matches carry list_type "crime" and set only the flagged field. Each match names which of the two lists it came from, and a domain on both returns two matches.

Screen against this list

Every /screen endpoint checks all enabled lists by default and names the list behind each match. Add the ?lists= filter to restrict a request to this source.

GET /api/v1/screen/website?address={url}&lists=scamsniffer,metamask_phishing

curl "https://api.compliapi.com/api/v1/screen/website?address=https://www.evil.example/claim&lists=scamsniffer,metamask_phishing" \
  -H "Authorization: Bearer $COMPLIAPI_TOKEN"

Response

{
  "value": "www.evil.example/claim",
  "flagged": true,
  "sanctioned": false,
  "lists_checked": ["scamsniffer", "metamask_phishing"],
  "matches": [
    {
      "list": "scamsniffer",
      "list_name": "ScamSniffer phishing domains",
      "list_type": "crime",
      "match": "partial",
      "value": "evil.example",
      "source_url": "https://github.com/scamsniffer/scam-database",
      "metadata": { "category": "phishing" }
    }
  ]
}

Frequently asked questions

Is a phishing-domain match a sanctions hit?

No. Both lists are community crime intelligence, not government designation lists. A match sets flagged: true with list_type "crime" and leaves sanctioned: false.

Where do the phishing domains come from?

From two public blocklists: the ScamSniffer scam database and MetaMask's eth-phishing-detect list, both published on GitHub. CompliAPI ingests each once a day and names the list on every match.

Why might a new phishing site not match yet?

ScamSniffer publishes its public file 7 days after detection, and CompliAPI ingests both lists daily. A site that appeared this week may be on neither list yet, so a clean result is not proof a site is safe.

Does a full URL match, or only the bare domain?

A full URL matches its listed host: the scheme, www., port, path and query string are ignored, and the match is reported as partial. Subdomains are not folded into their parent domain.

Can I download the phishing domain lists from CompliAPI?

No. Their licences do not allow republishing, so there is no bulk download and they do not appear in the free search. Screen single websites through the API, and take the full lists from ScamSniffer and MetaMask on GitHub.

Can I leave the phishing lists out of a website screen?

Yes. Pass the lists filter naming only the lists you want checked. By default every enabled list is checked, including both phishing lists.

Related

Screen against Phishing domains data

Get a free API key and make your first request in minutes — every screen checks all enabled lists in one call.

Free tier: 100 requests a month. No credit card required.

CompliAPI provides data and tools that support compliance workflows. It does not provide legal advice, and organizations should determine their obligations with qualified counsel.