Info signal

On-Chain Proxy

The contract delegatecalls into a separate implementation resolved on-chain from its proxy slots.

Analyzer: Bytecode Patterns
Slug: onchain_proxy

What it means

Beyond detecting a delegatecall, RektRadar resolves the actual implementation address on-chain from the standard proxy storage slots (EIP-1967, beacon, OpenZeppelin legacy, EIP-1822/UUPS) and analyses the implementation's bytecode - not just the proxy shell.

Why it matters

A proxy shell tells you almost nothing: the real logic lives in the implementation it points to. Following the proxy to its implementation is the only way to judge a token whose shell looks clean but whose logic is malicious (or can be swapped for malicious).

How RektRadar detects it

Reads the EIP-1967 implementation slot, falls back to the beacon (calls implementation() on it), the OpenZeppelin legacy slot, and the EIP-1822 PROXIABLE slot, then scans the resolved implementation's runtime bytecode.

From our dataset

411
tokens carried this flag
395
of them classified scam
96.1%
of tokens with this flag end up classified scam
8
flagged in the last 30 days

Top brand-jacked tickers carrying this flag: $TMASTER, $ENZF, $USDT, $ysUSDC, $ABBVx

Pool version of the flagged tokens that trade: V4 402 · V3 22 · V2 10

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

Recent tokens with this signal

Loading recent tokens…

Analyze a token →