RUG.TOOLS
Clash ($clash)
0xaf62a3c44363ce474cf90200e54dd7cf28b65985Scan results are a snapshot. Select Analyze Again to run a new scan.
5 of 8 analysis modules returned usable evidence on Ethereum. Some checks remain incomplete. Confirmed risk findings still apply; missing evidence does not establish safety.
Contract runtime was acquired, but its capabilities are not yet verified for this runtime family
Creator attribution unavailable
LP lock status could not be determined from available data
Limited — Sell simulation / honeypot screening resolved
Verified below: market observation (Market provider not recorded).
Rugged / Dead
The contract behaves like a honeypot — buyers cannot exit. Do not trade.
Scanned at 2026-10-22 16:56:16 UTC
Market conditions can change after a scan. Select Analyze Again to refresh.
Token controls unverified · Contract Holder Unclassified · LP protection unverified · Evidence needs refreshing · Holder evidence incomplete.
Verification gaps (11): Required verification checks are incomplete; category availability does not establish completed verification. · The report evidence is stale or its observation time is invalid; confidence is limited. · On-Chain Contract Checks: Contract runtime was acquired, but its capabilities are not yet verified for this runtime family · More in Evidence & Caveats below.
Evidence-backed reasons, ranked by recorded severity. Open Evidence & Caveats below for complete explanations and limits.
- Critical Red Flag
1. Project Lifecycle
Liquidity or market activity has collapsed.
Why it matters: Weakening activity or liquidity can impair exits; deterioration alone is not proof of deliberate fraud.
- Critical Red Flag
2. Contract Security
Honeypot — buyers cannot sell.
Why it matters: Restrictions on selling directly affect whether holders can exit; verify the exact tested route and observation time.
- High-Priority Risk
3. Unclassified Contract Concentration
An unclassified contract holds 70.04% of supply.
- Risk Indicator
4. Liquidity
Very thin liquidity ($83) — a trading risk (heavy slippage), not proof of a scam.
Why it matters: Limited available liquidity can make large trades expensive or difficult to exit; a market quote is not proof of LP protection.
Bottom line
The contract behaves like a honeypot — buyers cannot exit. Do not trade.
Biggest concerns
project lifecycle · contract controls
Evidence & Caveats 4 recorded reasons · 11 verification gapsClick to expandExpanded
Recorded verdict explanation
The contract behaves like a honeypot — buyers cannot exit. Do not trade.
Some checks unverified: Token controls unverified · Contract Holder Unclassified · LP protection unverified · Evidence needs refreshing · Holder evidence incomplete.
1. Project Lifecycle · Critical
Liquidity or market activity has collapsed. Lifecycle evidence alone does not confirm deliberate liquidity removal.
Why it matters: Weakening activity or liquidity can impair exits; deterioration alone is not proof of deliberate fraud.
2. Contract Security · Critical
Honeypot — buyers cannot sell.
Why it matters: Restrictions on selling directly affect whether holders can exit; verify the exact tested route and observation time.
3. Unclassified Contract Concentration · High
An unclassified contract holds 70.04% of supply. Its purpose and control remain unverified.
4. Liquidity · Medium
Very thin liquidity ($83) — a trading risk (heavy slippage), not proof of a scam.
Why it matters: Limited available liquidity can make large trades expensive or difficult to exit; a market quote is not proof of LP protection.
Evidence quality & missing verification
Data available: 5/8 modules. Data availability does not mean every required check was verified.
Confidence describes evidence quality, coverage and freshness.
- Required verification checks are incomplete; category availability does not establish completed verification.
- The report evidence is stale or its observation time is invalid; confidence is limited.
- On-Chain Contract Checks: Contract runtime was acquired, but its capabilities are not yet verified for this runtime family
- Creator intelligence: Creator attribution unavailable
- LP ownership: LP lock status could not be determined from available data
- critical contract-security fields are unknown
- a major holder is an unresolved contract
- no verified locked or burned LP position was detected
- the underlying evidence is stale and has not been re-verified
- holder concentration requires recomputation from verified infrastructure roles
- An unclassified contract holds 70.04% of supply. Its purpose and control remain unverified.
Ruggy commentary
“This project is done. Don't step in the trap.”
Follow Rug.Tools & discuss this report
Discuss in Discord ↗Coverage note: Liquidity protection is unverified. No verified locked or burned LP position was established.
Market snapshot & additional signals
Market snapshot & key evidence
Total tracked liquidity
$83.12
Combined across tracked pools. Individual pools can have much less liquidity; the total is not an executable exit quote.
Market snapshot · · Snapshot values are not live quotes.
Per-pool amounts were not recorded in this snapshot. The total must not be read as the primary pool's liquidity.
Important signals
Recorded facts · open cards for evidenceSampled holder accounts: 99.9% · lower bound after infrastructure exclusions
No protective claim without on-chain proof
Risk findings remain visible even when other modules lack evidence. Open the full report for wallet, contract, creator and liquidity sources.
Detailed reportFull analysis & source evidenceWallet links, holder distribution, liquidity protection, creator activity, contract controls and source evidence.Expand full analysis ↓Collapse full analysis ↑
Supplemental intelligence
Provider and wallet context
GMGN intelligence
Independent token signals. The Rug.Tools verdict stays based on its own analysis.
Native launch analysis reconstructs a sampled launch-window wallet cohort as a percentage of token supply. GMGN bundler activity estimates a share of trading volume using its own wallet tags; its observation window and population are not established as equivalent. No native pattern in a sample does not rule out GMGN activity. Neither signal alone proves shared funding, bundle execution or insider ownership.
GMGN has not returned data for this token. Your scan and verdict remain available.
Wallet Trade Context
Loading trade context separately from your scan…
Pending ActivityEXPERIMENTAL
Sampled mempool observations, not continuous monitoring. Transactions may fail, be replaced, be cancelled or never confirm. Simulation does not prove confirmation or a completed trade. Pending evidence never changes the main verdict.
Reading stored pending observations…
Risk Snapshot
Report overviewRisk Snapshot
The most important report signals in one place. Detailed evidence stays below; this presentation does not recompute or alter the canonical Rug.Tools verdict.
An unclassified contract holds 70.04% of supply. Its purpose and control remain unverified. Currently sits at $83 in liquidity, $0 traded in the last 24h, 40 holders. The creator wallet could not be verified.
Why this verdict?▾
- Critical overrideProject LifecycleLiquidity or market activity has collapsed. Lifecycle evidence alone does not confirm deliberate liquidity removal.
- Critical overrideContract SecurityHoneypot — buyers cannot sell.
- + High riskUnclassified Contract ConcentrationAn unclassified contract holds 70.04% of supply. Its purpose and control remain unverified.
- + ConcernLiquidityVery thin liquidity ($83) — a trading risk (heavy slippage), not proof of a scam.
- NeutralLargest Holder AccountLargest sampled holder account holds 70.04%; independent control is unverified.
- NeutralSampled Holder Accounts10 sampled accounts hold 99.86% in total; this is a lower bound when the filtered sample has fewer than ten accounts.
Key Findings
😈 Rugged / DeadHoneypot detected — cannot sell after buying.
The security scan flagged this contract as a honeypot: buys succeed but sells revert. Treat as an active scam.
An unclassified contract holds 70.04% of supply.
Independent control and purpose remain unverified.
Trading risk: very thin liquidity — even small trades will move the price.
This is a liquidity/slippage risk for traders, not evidence that the token itself is unsafe.
Liquidity protection is unverified.
Liquidity protection is unverified. No verified locked or burned LP position was established.
Show all 5 findings
- Reasonable trading tax (0.0% buy / 0.0% sell).
Live Market Context
Market & trading
Live Market Context
Price, liquidity, volume, venue and trading-tax context are grouped here instead of being repeated across the report.
Market Snapshot
Market activity
Recent trades and participating wallets · Birdeye
Loaded only when requested. No background refresh.
Holders & connected wallets
Wallet intelligenceWallet & Distribution Intelligence
Current holder concentration, connected-wallet evidence and launch-window coordination are kept together so current ownership is not confused with historical launch exposure.
Account control unresolved · major contract holding unresolved. Adjusted concentration excludes identified pools and burn sinks; other custody is retained when independent control is unverified.
Connected Wallet Intelligence
Reading cached wallet relationships…
Native evidence explorer
Launch, wallet flows & liquidity custody
Inspect what was observed, which balances were measured, and what remains unverified. Timing and transfers alone do not establish common ownership or a sale.
Investigate creator trades & token transfers
Forensic intelligence / Activity
What did the developer actually do?
Separate current holdings, historical launch exposure, verified sales and token transfers. Follow the receipts before drawing conclusions.
- Creator holdings
- Unknown
- Historical launch exposure
- Unknown
Saved balance measurement; separate from sale history
Observed launch-group share of total token supply; not every graph node, developer sales or present insider ownership
Developer sales: Insufficient Evidence · Trading integrity: Not Scored. A creator holding 0% does not establish whether tokens were sold or transferred.
Launch evidence
0 stored cohort rows
Receipt-level replay was not stored for this snapshot.
Current cohort balances
Unknown
Recipient cohort not recorded
Custody coverage
1 custody accounts / markets
1 without verified protection
Token custody and LP withdrawal protection are separate checks.
Launch timeline & receipt references
This older snapshot contains a recipient cohort, not the full receipt timeline. Counts and timing describe only the stored sample. Exact interval supply figures and transaction references remain unknown until a bounded native replay records them.
Pool-by-pool custody & protection
Pool allocation not established · reported role / market
Market selection alone does not verify LP ownership, locks or the controller of this pool.
Measured wallet balances & transfer evidence
A measured zero balance does not prove a sale. Unknown balances are not zero. Only 0 stored sample rows are listed; aggregate coverage includes missing rows.
| Recipient | Current balance | First position | Receipt references |
|---|
Source snapshot: . This evidence explorer does not independently change the Rug.Tools verdict. Existing risk findings, verification gates and source timestamps remain authoritative.
RugGraph / Wallet intelligenceLinked-wallet graph10 wallets · 0 transaction references. Follow the receipts from saved launch evidence.Open wallet graph ↓
01 / Launch activity
Select a wallet to see its activity near token launch. Early receipt of tokens alone does not prove a sniper purchase.
Cyan: tokens received · Amber: tokens moved out · Dashed: deployment. Lines connect wallets to the launch sample; they do not identify who sent the tokens.
0x0d65faf891c0d7dfa3edb98611e5a24f5ff45f22
Major holder
Balance at last observation
70.04%
2026-10-22 16:56:14 UTC · observation, not a live balance
No transaction reference was stored for this wallet. No relationship is inferred.
02 / Funding connections
Where did the funding come from?
Follow verified transfers back up to three wallets. Select any connected wallet to explore its evidence.
Evidence first. Ownership stays unproven.
A transfer proves funds moved between addresses. It does not prove they belong to the same person. Known exchange, bridge and pool accounts are marked as infrastructure.
How to read this evidence
Arrows show receipt references associated with the launch sample. They do not identify transfer counterparties or establish common ownership.
An early recipient is not necessarily a buyer or sniper. Outflows may be transfers; these summaries do not establish realized sales.
Balance measurements retain their original timestamps. Historical launch exposure is separate from present holdings.
Funding paths, verified swap activity and volume manipulation require additional transaction evidence. Missing history is unknown.
Source snapshot: 2026-10-22 16:56:16 UTC · Funding research runs only when requested.
Launch activity
Launch exposure, linked wallets and current holdingsNo Coordinated Launch Signal Observed
Module severity describes launch-pattern evidence and does not replace the overall Rug.Tools verdict.
Reconstructed from ERC-20 Transfer logs in the first 5,000 blocks after deployment. Initial distribution includes pools, lockers and other protocol contracts and is not evidence of insider control. Wallet exposure counts only non-contract recipients, and wallets are reported as coordinated only when they acquired supply in the same block.
Creator intelligence
Developer intelligenceDeveloper / Creator Intelligence
Creator attribution, current holdings, external creator facts and wallet-link evidence are correlated here without changing the canonical Rug.Tools verdict.
May refer to a different wallet or observation time. Reported exits do not establish verified sales or override measured on-chain holdings.
GMGN supplemental intelligence unavailable for this token right now
Developer network could not be fully verified
Wallet-link evidence is incomplete. Missing evidence is not treated as safe.
Incomplete wallet evidence does not lower the overall risk verdict.
Inspect wallet links & supporting evidence▾
No relationship evidence was strong enough to list.
Coverage note: connected-wallet relationships are still loading.
Wallet relationships are one risk category. The overall Rug.Tools verdict can still be High Risk because of contract controls, trading restrictions, liquidity, holder concentration, or other evidence. A dominant holder is a concentration risk; one large wallet alone is not proof that several wallets are connected.
Presentation-only · does not independently change the Rug.Tools verdict
Liquidity & LP Protection
LiquidityLiquidity & LP Protection
Trading depth and LP ownership/lock evidence are grouped together. Liquidity depth describes trading conditions; LP protection describes whether liquidity ownership can be verified.
LP lock or burn protection has not been verified. Missing evidence does not mean liquidity is unlocked.
Ownership, protection & source evidence
No LP holder or lock data was returned for this token, so liquidity protection is Unknown rather than estimated. Unverified LP is a potential signal only and is not counted as evidence of a rug on its own.
Protection applies only to the measured pool or position; it does not establish overall token safety.
Source: On-chain LP holders
Contract & trading controls
ContractContract Controls
Direct contract and security-provider evidence. Unknown capabilities stay unknown and are never silently treated as safe.
Historical Pattern Review
Historical intelligence
Historical Pattern Review
Optional read-only comparison against archived launches and developer patterns. It never changes the Rug.Tools verdict or risk score.
Challenge this report with historical patterns
Runs only when you ask. It compares stored launch and developer patterns and may add an AI adversarial review. It never changes the Rug.Tools verdict or risk score.
Sources & coverage
Evidence quality
Analysis Coverage
Core report evidence and extended intelligence are separated so a complete core report cannot be confused with an unavailable optional launch-history module.
Usable evidence can be partial. These counts do not mean every contract permission, sell restriction or liquidity position was verified.