Skip to content
HexScan logo

HexScan

Checks any ERC-20 token for honeypot traps, rug-pull risk, malicious taxes and holder concentration, returning a 0-100 risk score.

Actively maintained

At a glanceswept Oct 26, 2026

not read yet

Use

For
Traders and developers checking whether an ERC-20 token is a honeypot or rug before buying it.
Activity
Actively maintainedrelease 5 weeks ago
Runs as
API
Used for
  • Check an ERC-20 token for honeypot and rug-pull signs
  • Review unverified source code and holder concentration risk
  • Screen tokens across several EVM chains via API
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 26, 2026

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Securityby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare HexScan with

Pick up to two.

All 10 alternatives to HexScan →

All Security tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use HexScan for?

Sign in to leave a note
Questions this page answers
  • What is HexScan?

    Checks any ERC-20 token for honeypot traps, rug-pull risk, malicious taxes and holder concentration, returning a 0-100 risk score. It is listed in the Atlas under Security.

  • Who is HexScan for?

    Traders and developers checking whether an ERC-20 token is a honeypot or rug before buying it.

  • Do people use HexScan?

    Little sign of use.

  • Is HexScan still maintained?

    Actively maintained: release 5 weeks ago.

  • What are alternatives to HexScan?

    In Security, by use: Strix, XposedOrNot, Hacktron AI, FaceSign, Eosl, Hiddencontent.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk