tok{In} ERC20 Weekly Security Intelligence Report

September 28, 2026 – October 4, 2026

Previous week, September 21, 2026 – September 27, 2026Next week, October 5, 2026 – October 11, 2026
Weekly Snapshot: tokens analyzed
249,301
Ethereum
4,278
Base
37,767
BNB Chain
106,008
Robinhood Chain
101,248

Rows marked with an arrow open to show which launchpads the tokens came from and the tokens themselves. The tokens are as measured when the week was published: a scan today can show a different result, because pools, owners and settings change. A liquidity figure that is struck through cannot be true: a price feed probably gave the pool the price of another asset.

All Chains

32 checks
The share of the week's tokens that carry each flag, on every chain together and on each chain
CheckAll ChainsEthereumBaseBNB ChainRobinhood Chain
Trade Simulation
6.2%20% (well above All Chains)2.2%6.8%3.4%
9.3%2.9%11%6.4%11%
<0.1%0.0%0.0%0.0%0.1%
Transfer Blocked0.0%0.0%0.0%0.0%0.0%
Trading Restrictions
Counted by the old rule: a tax that the token moves through its shared transfer function, or writes as amount / (100 / fee), did not count.61%51%50%93% (well above All Chains)32%
Counted by the old rule: a setter that only a misread constant made, or a write from transfer itself (such as the total supply), could count. Also, a setter of such a tax (a shared transfer function, or amount / (100 / fee)) did not count.0.2%0.8%0.2%0.1%0.2%
1.4%5.4%2.0%0.3%2.3%
Counted by the old rule: the limit of a number type (uint192 to uint248, the limit of a cast), which no trade can reach, counted as a trading cap. Also, a stored value that is only an overflow test or the whole supply counted as a trading cap.8.0%29% (well above All Chains)12%1.6%12%
Counted by the old rule: a setter that only a misread constant made, or a write from transfer itself (such as the total supply), could count. Also, a function that writes such a value (an overflow test or the whole supply) counted as a trading cap setter.6.9%22% (well above All Chains)8.0%1.4%12%
0.2%0.8%0.1%<0.1%0.5%
Counted by the old rule: a stored value that is only an overflow test or the whole supply counted as a position cap.2.9%11% (well above All Chains)1.1%0.1%6.1%
Counted by the old rule: a setter that only a misread constant made, or a write from transfer itself (such as the total supply), could count. Also, a function that writes such a value (an overflow test or the whole supply) counted as a position cap setter.2.4%1.7%0.1%0.1%5.8%
Counted by the old rule: the block number of a vote checkpoint, which every transfer writes, counted as a cooldown.<0.1%0.6%0.1%<0.1%<0.1%
Access Controls
Counted by the old rule: a check that runs only when tokens are minted or burned, such as the total-supply vote checkpoints, counted as a list.9.7%12%8.7%12%8.0%
Counted by the old rule: a lock that a transfer sets and clears in the same call counted as a pause.1.2%6.1%3.8%0.6%0.7%
Counted by the old rule: a setter that only a misread constant made, or a write from transfer itself (such as the total supply), could count. Also, a function that only sets and clears a transfer lock, or only clears a flag that never blocks, counted as a pause setter.1.0%5.1%3.3%0.3%0.6%
0.1%1.0%<0.1%<0.1%0.2%
70%35%67%95%47%
Counted by the old rule: a check that runs only in a mint or burn branch that transfer can never enter, or a lock that transfer sets and clears, counted as a guard.16%36% (well above All Chains)22%13%15%
Counted by the old rule: a check that runs only in a mint or burn branch that transferFrom can never enter, or a lock that transferFrom sets and clears, counted as a guard.16%36% (well above All Chains)22%13%15%
Contract Behaviour
20%29%33% (well above All Chains)23%11%
Counted by the old rule: a type limit or a zero compared with the time counted as a deadline, and a deadline in a packed field and a time check inside a small helper did not count.8.0%12%17% (well above All Chains)6.2%6.4%
View Modifies State0.0%0.0%0.0%0.0%0.0%
Supply & Lifecycle
Counted by the old rule: a burn that only the holder, or a spender within the holder's allowance, can make counted as a mint or burn.36%39%58% (well above All Chains)7.3%59% (well above All Chains)
<0.1%0.1%0.0%<0.1%0.0%
Token Profile
94%86%83%99%94%
12%8.9%23% (well above All Chains)17%1.9%
59%1.8%44%89%36%
49%45%38%52%50%
1.1%11%2.6%0.2%1.0%
99%96%97%>99%>99%
Code Analysednot measurednot measurednot measurednot measurednot measured

1.5 times the All Chains share or more, and 5 points above it

Static analysis version: 1.0.17 for 73% of the tokens, 1.0.19 for 27% of the tokens, 1.0.18 for <0.1% of the tokens. A newer version can change what a static-analysis figure counts, so part of this week is counted under each meaning.

Honeypot: Bought, Cannot Sell

171 (6.2% of liquid)

Launchpads

Where the week's tokens came from, and how often each launchpad's tokens carry a flag

Honeypot: Bought, Cannot Sell: the rate of each launchpad's tokens on All Chains, against all tokens
LaunchpadTokensHoneypot: Bought, Cannot Sell
All tokens249,3016.2%
Flap
83,0583.0%
four.meme
34,2730.0%
Doppler
13,6187.1%
Zora
12,1820.0%
Lunch.fun
622— too few to rate
Pools.trade
5792.1%
Pons
4790.6%
Clanker
449— too few to rate
No launchpad match102,4876.9%

A token is matched to a launchpad by a stored scan, its bonding-curve pool, its deployer, its bytecode or its address. “No launchpad match” does not prove that a token came from no launchpad. Rates marked ▲, in amber, are well above the chain's own. A rate is not shown under 20 tokens, and a launchpad needs 50 tokens for a row.

Live token screening

Want the risk profile for a token right now?

Run a free tok{In} scan to surface honeypot behavior, transfer restrictions, privileged controls, and pool-specific risk signals before users interact.

Scan a Token Now Free