← All signals / ← Tous les signaux

Danger signal

Hardcoded Address Blacklist

The transfer path reverts for specific addresses baked into the code.

Analyzer: Source-Code Analysis
Slug: hardcoded_address_blacklist

What it means

The _transfer implementation reverts when from/to equals a hardcoded address. No mapping, no setter to watch - the trap is compiled in.

Why it matters

Hardcoded blacklists survive every ownership renounce and admin-function audit: the control is in the bytecode itself. Victims are chosen before deployment.

How RektRadar detects it

Source regex on _transfer bodies comparing against literal addresses then reverting, raised as danger.

From our dataset

2,597
tokens carried this flag
2,195
of them classified scam
84.5%
of tokens with this flag end up classified scam
320
flagged in the last 30 days

Top brand-jacked tickers carrying this flag: $VALE, $DSGT, $CCO, $TAD, $FLNT

Pool version of the flagged tokens that trade: V2 1,955 · V4 5

Snapshot from RektRadar's token_analysis database as of 2026-08-17.

Recent tokens with this signal

Loading recent tokens…

Analyze a token →

Related signals

Blacklist Mapping - The contract can blacklist any address from selling - a kill-list with no notice period. Owner Not Renounced - The contract still has an owner - nothing prevents a future privileged change. Upgradeable Proxy - The contract is a proxy - its logic can be swapped without users' consent. Proxy Admin Role - An admin role exists and can change the proxy's implementation contract. Beacon Proxy - Multiple contracts share a single upgradeable implementation - one switch rugs all of them.