LEEK Meme Coin Risk Analysis & Trade Setup

LEEK Risk Analysis and Trade Setup Summary

Overall Health Score: Justice for CyberLeek has an Overall Health Score of 32 out of 100.

Rug Risk Rating: Justice for CyberLeek has a low Rug Risk Rating. This reflects collected on-chain evidence and is not a safety guarantee.

LEEK Rug-Pull Risk Analysis

• Whale (>1%) and big (0.1–1%) sellers together accounted for ~74% of all sell volume over the 22-hour window (~$332M tokens sold), far outpacing buy-side inflows. Net volume is -$76.9M tokens, and the 1-hour window also shows sell dominance with 118 sell txns vs 95 buys.
• Price has dropped 58.94% in 24 hours and 48.82% in just 6 hours, reflecting a post-launch dump with no signs of stabilisation. The nearest computed support at $0.0000830 has only 1 touch and low strength (45), offering weak confidence as a base.
• All whale holders entered within the last 24 hours with an average holding duration of 0.84 days; "accumulating" and "never sold" signals have no durability context whatsoever and cannot be treated as bullish conviction at this age.

LEEK Risk and Health Signals

• Both mintAuthorityActive and freezeAuthorityActive are false with null authorities, and tokenControls shows no active or dormant dangerous extensions — the contract-level control risk is clean.
• The cluster analysis returned an empty array, meaning no coordinated insider wallet networks have been identified from shared funding or direct token transfers among the top holders.
• Excluding the liquidity pool, the top 10 holders control 12.4% and top 20 control 18.8% of supply, with the largest single non-pool wallet (D5Zc…ENC) at only 2.16% — not extreme for a launch-stage token.

LEEK Holder Distribution

Holder concentration: The top 10 non-pool holders control 12.4% of supply.

Is LEEK Safe?

• Creator risk check: no blacklist match found.
• Wash-trading check: no suspicious activity detected.
• Copycat check: no match detected.
• Sellability check: a sell route was observed.
• Smart-money check: no tracked participation was observed.

LEEK Trade Setup, Entry Levels and Targets

Support and resistance context: 2 support areas and 4 resistance areas were identified from 15m market candles; nearest support: 0.00008303544615257968; nearest resistance: 0.00009658296720988147; Levels derived from 98 15m candles (~24 hours) of pool price history via swing-point clustering. Heuristic zones, not trading advice..

LEEK Price and Market Data

Assessment: LEEK is a ~1-day-old PumpSwap memecoin that has shed roughly 59% of its value in 24 hours, dropping from a launch spike to a current market cap of ~$88K with liquidity of ~$27.8K — a 31% liquidity-to-market-cap ratio that is thin but functional at this size. Mint and freeze authorities are both revoked, no dangerous token extensions are active, and no wallet clusters have been detected, which are the cleanest structural signals present. However, the token is experiencing heavy net sell pressure: over the last 22 hours, whale-tier wallets (>1% supply) generated 33% of all sell volume by token count, and big wallets (0.1–1%) added another 41%, meaning roughly 74% of sell volume came from large holders even as the holderIntel labels all tracked whales as "accumulating" — the apparent contradiction likely reflects high turnover at these sizes rather than genuine long-term conviction. The decentralisation trend is worsening, all whale holding durations average under one day, and the price has not found a stable floor yet; at this age there is zero track record and every structural reading should be treated with maximum caution.

Reason: A 1-day-old token down 59% with 74% of sell volume sourced from large wallets, a worsening decentralisation trend, and a thin $27.8K liquidity pool has no demonstrated durability and carries dominant sell-side structural risk.

Report limitations

• This automated snapshot can be wrong, incomplete, or become outdated as on-chain and market conditions change.
• It is informational analysis, not financial advice or a guarantee that the token is safe.