← All signals / ← Tous les signaux

Warning signal

Beacon Proxy

Multiple contracts share a single upgradeable implementation — one switch rugs all of them.

Analyzer: Source-Code Analysis
Slug: beacon_proxy

What it means

A beacon proxy reads its implementation from a shared `Beacon` contract. Many tokens can be deployed against the same beacon, and one upgrade affects every dependent contract simultaneously.

Why it matters

Beacons are a rug force-multiplier. The operator deploys 50 tokens against one beacon, builds liquidity over weeks, then upgrades the beacon to a malicious implementation, draining all 50 at once.

How RektRadar detects it

Bytecode signature for `BeaconProxy` (`getImplementation()` via beacon) plus storage slot inspection.

From our dataset

58
scam tokens carrying this flag
100.0%
of tokens with this flag end up classified scam
38
flagged in the last 30 days

Top brand-jacked tickers carrying this flag: $GCRM, $ADIon, $AMGNon, $ANETon, $BAon

Snapshot from RektRadar's token_analysis database as of 2026-05-25.

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. UUPS Proxy — The implementation contract holds its own upgrade logic — accidental brick risk plus rug risk.