Wallet risk checker

What this page covers, and what it does not

Searches for a wallet risk checker usually mean one of two different things. The first is 'is this address that a contract belongs to, or that holds power over it, a risk to me' — that question ScanZX answers, as part of a token scan. The second is 'is my own wallet compromised, and what is my portfolio exposed to' — that question ScanZX does not answer at all, and this page is not going to imply otherwise.

Concretely: the scanner takes a token contract address. If you give it an address with no contract code it returns 'No contract code found at this address' and stops. There is no portfolio view, no approval-revocation tool, and no personal-wallet risk score anywhere in the product. If that is what you need, you need a different tool, and it is better for you to learn that here than after signing up.

What you do get is the wallet analysis that surrounds a token: who created the contract, what else they created, who holds administrative power over it now, what kind of account that is, and how supply is spread across holders.

Deployer address checks

The deployer is the address that created the contract. ScanZX resolves it from chain and explorer data, then looks it up against its own scan history: how many other tokens from this address has ScanZX seen, and how many of those did it score at or above the high-risk boundary of seventy.

The relationship used here is deliberately narrow. A deployer counts as risky because a token it deployed was previously scored high risk by this system — not because it once received funds from an address somebody flagged, and not because a third-party list says so. Transaction-proximity reputation produces confident-sounding findings that fall apart on inspection, and a risk product that publishes those trains people to ignore it.

The consequence is that this signal is only as deep as ScanZX's own history. For a deployer this instance has never seen, the honest answer is that there is no history, and that is what the report says — an empty record is reported as an empty record, never as a clean one.

Owner and authority checks

Separately from who created the contract, ScanZX reports who currently controls it. That means the owner address, whether ownership has been renounced, whether the contract exposes a route to take ownership back, and whether an owner is hidden behind an indirection rather than exposed in the standard place.

The owner's account type is reported where it can be established: an externally-owned account, a multisig, a timelock or another contract. This distinction does more work than most people expect. One key that can pause trading in a single transaction is a different exposure from a multisig requiring several signers, which is different again from a timelock that publishes an intended change before it can execute.

Holder-side wallet analysis is covered on its own page — see token holder analysis for how concentration and clustering are measured.

What a finding proves — and what it does not

Limitations

• The scanner rejects addresses with no contract code, so a plain wallet address cannot be scanned at all.
• Deployer history is built only from this instance's scan history and is thin for addresses it has not seen.
• Owner detection relies on standard interfaces. A contract that manages authority through a non-standard mechanism may report its owner as unknown, which lowers confidence rather than raising the score.
• Wallet labels of every kind are heuristic. Treat them as prompts to look further, not as conclusions.

Any check that cannot run is listed in the report as unavailable and lowers its confidence score — it never lowers the risk score. The methodology page sets out how the weights and the confidence model work, and the status page shows which providers are configured.

Common questions

Chain coverage

The deep EVM scan runs on five chains. Each chain page lists which checks are configured there and the risk patterns that recur on it.

Related reading and checks

Guides that go deeper on this subject:

• Deployer history and why it matters — What a deployer's past tokens can show, and the reputation shortcuts worth refusing.
• Owner privileges explained: mint, pause, blacklist — The contract powers that decide whether your position is really yours.
• What does renounced ownership mean? — Why renouncing reduces some admin risk but does not settle a review.

Other checks in the same report: