On-chain security analysis — is it a scam or legit?
EthereumYellowToken is a standard ERC-20 implementation utilizing OpenZeppelin's ERC20Permit and EIP712 standards.
Read the full analysisEach factor is an on-chain fact recorded at the time of this analysis. The score is computed from them by a deterministic function, so the same contract returns the same score for anyone who runs the audit. How scores are computed
Share held by contracts — treasury, vesting, bridge or staking — is discounted against share held by wallets when the score is computed: a contract cannot decide to sell the way an anonymous holder can, though it can still be drained or voted to sell. Effective concentration is the figure the risk score is actually calculated from.
Holder balances as recorded by the audit of Oct 21, 2026
The risk score reads depth across every pair.
The LP tokens of the analysed pool are not locked or burned, so whoever holds them can withdraw that liquidity.
0x1ec1…ffb30xf385…5f850.0% of the pool's LP is burned or time-locked. 100.0% is held, unlocked, by 1 address(es) other than the owner/deployer. One of them — a contract, 0x1ec1…ffb3 — holds 100.0% and can remove that share at once; who controls it is not visible on-chain, so it is not treated as an independent provider. Some pools are concentrated-liquidity (V3/V4) positions; shares above are by position as GoPlus reports them. This assessment covers the main pool, which holds 55% of the token's DEX liquidity; the other pools were not assessed.
Check the lock's end date and beneficiary on the locker's own page before relying on it.
Acknowledged
The verified source code was reviewed and no issue rising to Informational severity or above was identified. This is a statement about the code that was read, not a guarantee: the review covers the published source only. Fact-layer checks (mint capability, holder concentration) were applied separately and feed the risk score.
Re-check after any contract upgrade or ownership change, both of which can alter behaviour without changing this page.
Acknowledged
The ten largest holders own 99.6% of supply. What remains: 1.5% in wallets, 98.1% in other contracts. 2,349 holders in total.
Watch the largest wallets that are not exchanges, pools or locks — those are the ones that can move the price.
Acknowledged
Listed on CoinGecko as Yellow (YELLOW), market cap $13M, rank #1061. 2,349 holders.
Match the contract address against the project's official channels before trading.
Acknowledged
Liquidity $139K (DexScreener, all pools). 24h trading volume $826K (CoinGecko, all markets, daily snapshot). 24h trading volume $187K (DexScreener, all pools).
Size any position to the liquidity and daily volume shown — they set how much you can sell and at what price.
Acknowledged
A token issued by a project for use, governance or fundraising. Scored on its contract and market facts. The class itself adds no points; the contract and market facts decide the score. Basis: no class-specific evidence. Tokenomics — Supply: fixed — the contract has no mint function. Control: an owner that could not be resolved. Code: not upgradeable (no proxy). Fees: no buy or sell tax. Market: $139K of DEX liquidity across 5 pools. Launch: 215 days of market history.
Check the project's own documentation for what the token is used for; this report covers what the contract allows.
Acknowledged
YellowToken is a standard ERC-20 implementation utilizing OpenZeppelin's ERC20Permit and EIP712 standards. The contract follows established industry patterns for token functionality and does not contain any privileged administrative roles or custom transfer logic. No vulnerabilities were identified during the static analysis of the source code.
The architecture follows the standard OpenZeppelin ERC-20 implementation, ensuring high compatibility with existing DeFi protocols. 7.1 Architecture is modular and 7.2 Code Security is robust due to the use of audited library code. 7.3 Access Control is non-existent as there are no administrative functions, which eliminates central points of failure. 7.6 External dependencies are limited to standard, well-vetted libraries.
7.4 Economic and 7.5 Governance factors are not applicable as the token lacks minting, burning, or fee-based mechanisms. The token supply is fixed upon deployment, and there are no governance-controlled parameters. 7.8 Operations are straightforward, relying entirely on standard ERC-20 behavior.
The contract is not a proxy and is immutable, meaning 7.7 Upgrades are not possible. This eliminates risks associated with proxy logic, storage collisions, or malicious implementation updates. The contract state is permanently defined by the initial deployment.
The contract is well-structured and follows best practices for a standard ERC-20 token.
No further action is required as the code is secure and lacks complex logic that could introduce vulnerabilities. Users should ensure that they interact with the correct contract address and verify the token's total supply and distribution through block explorers to confirm the intended economic state.
Free for any token on the record. It links to this page and always shows the current score and the date it was checked.
Score changes are recorded as dated snapshots — history is append-only and cannot be edited.
Our AI-powered scanner gives you a deeper, real-time smart contract analysis — free, with every scoring factor shown.
Get Detailed Audit Is this your token? Publish your own audit on this page
