RUG.TOOLS
ETAS (ETAS)
0x425d01bae2f1fbb694247befef7270429d33727bScan results are a snapshot. Select Analyze Again to run a new scan.
4 of 8 analysis modules returned usable evidence on Base. Some checks remain incomplete. Confirmed risk findings still apply; missing evidence does not establish safety.
Required native contract evidence could not be fully verified
No active market pair verified
LP lock status could not be determined from available data
Liquidity depth could not be verified
Limited — Sell simulation / honeypot screening resolved
Rugged / Dead
The contract behaves like a honeypot — buyers cannot exit. Do not trade.
Scanned at 2026-10-05 22:23:28 UTC
Market conditions can change after a scan. Select Analyze Again to refresh.
Token controls unverified · LP protection unverified · Evidence needs refreshing · Holder evidence incomplete.
Verification gaps (14): 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. · Launch-pattern confidence does not verify funding relationships, common ownership or bundle execution. · 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. 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.
- Risk Indicator
2. Coordinated Wallet Activity
A possible coordinated early-buyer pattern was observed; wallet coordination and insider attribution are not confirmed.
Why it matters: Historical launch exposure can create concentration risk. It does not establish current balances, common wallet control, or executed bundles.
Bottom line
The contract behaves like a honeypot — buyers cannot exit. Do not trade.
Biggest concerns
contract controls · launch-wallet activity
Evidence & Caveats 2 recorded reasons · 14 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 · LP protection unverified · Evidence needs refreshing · Holder evidence incomplete.
1. 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.
2. Coordinated Wallet Activity · Medium
A possible coordinated early-buyer pattern was observed; wallet coordination and insider attribution are not confirmed.
Why it matters: Historical launch exposure can create concentration risk. It does not establish current balances, common wallet control, or executed bundles.
Evidence quality & missing verification
Data available: 4/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.
- Launch-pattern confidence does not verify funding relationships, common ownership or bundle execution.
- 6/1691 launch-wallet balances measured; 1685 remain unknown. Present group holdings are not fully measured.
- On-Chain Contract Checks: Required native contract evidence could not be fully verified
- Market data (DexScreener): No active market pair verified
- LP ownership: LP lock status could not be determined from available data
- Liquidity depth: Liquidity depth could not be verified
- critical contract-security fields are unknown
- 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
- Liquidity: Liquidity data unavailable.
- Project Lifecycle: Not enough data to judge lifecycle.
Ruggy commentary
“Caught this one red-handed. Stay far away.”
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
Primary pool · venue unknown
Not recorded
Total tracked liquidity
Not recorded
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 evidenceHistorical acquisition; current holdings are a separate measure.
Sampled holder accounts: 90.5% · 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…
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.
The contract behaves like a honeypot — buyers cannot exit. Do not trade. Currently sits at 1.7K holders. Top holder sits at 13.6% and a launch-wallet pattern was detected; funding relationships, common ownership and bundle execution remain unverified. The creator wallet is identified.
Why this verdict?▾
- Critical overrideContract SecurityHoneypot — buyers cannot sell.
- + ConcernCoordinated Wallet ActivityA possible coordinated early-buyer pattern was observed; wallet coordination and insider attribution are not confirmed.
- No dataLiquidityLiquidity data unavailable.
- No dataProject LifecycleNot enough data to judge lifecycle.
- NeutralLargest Holder AccountLargest sampled holder account holds 13.60%; independent control is unverified.
- NeutralSampled Holder Accounts10 sampled accounts hold 90.46% 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.
Extreme trading tax (0.0% buy / 100.0% sell).
Taxes above 15% will eat most of a normal trade and are a strong exit-scam signal.
Liquidity protection is unverified.
Liquidity protection is unverified. No verified locked or burned LP position was established.
No active trading pair found for this token.
No live pool was found on this chain, so the token cannot currently be bought or sold on a tracked DEX. This is normal for pre-launch or abandoned tokens.
Show all 5 findings
Identified creator wallet currently holds 3.0% of supply.
This measures only the identified creator wallet; total team or connected-wallet ownership is not established by this metric.
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.
High Concentration. 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
- 2.97%
- Historical launch exposure
- 14.33%
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
60 stored cohort rows
Receipt-level replay was not stored for this snapshot.
Current cohort balances
At least 65.31%
6/1691 wallets measured · 1685 unknown
Custody coverage
0 custody accounts / markets
0 without verified protection
Token custody and LP withdrawal protection are separate checks.
Creator provenance
0x24c1…c1fe · 2.97% current measured holdings
Attribution: rpc-creation-trace. Identified wallet only; this does not establish total team ownership.
Deployment receipt: 0xf70d…69f0
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
No position-level custody evidence is stored. This does not establish that liquidity is absent or protected.
Measured wallet balances & transfer evidence
A measured zero balance does not prove a sale. Unknown balances are not zero. Only 40 stored sample rows are listed; aggregate coverage includes missing rows.
| Recipient | Current balance | First position | Receipt references |
|---|---|---|---|
| 0xfd92…7eda | 13.60% | #51,554,363 | Not stored |
| 0xbaed…439f | 13.21% | #51,554,400 | Not stored |
| 0x3304…566a | 13.05% | #51,554,340 | Not stored |
| 0x1985…5c87 | 12.67% | #51,554,331 | Not stored |
| 0x0d07…92fe | 12.59% | #51,554,322 | Not stored |
| 0x0685…4469 | Unknown | #51,556,328 | Not stored |
| 0xcfdd…586f | 0.20% | #51,554,678 | Not stored |
| 0x2acf…2501 | Unknown | #51,556,436 | Not stored |
| 0xc7c1…6d01 | Unknown | #51,556,419 | Not stored |
| 0xd0d1…7c6b | Unknown | #51,556,548 | Not stored |
| 0x194a…f3fd | Unknown | #51,556,585 | Not stored |
| 0x8fbb…fdcc | Unknown | #51,556,469 | Not stored |
| 0x71f5…39a4 | Unknown | #51,556,452 | Not stored |
| 0x4572…a43d | Unknown | #51,556,429 | Not stored |
| 0xa3c0…affe | Unknown | #51,556,403 | Not stored |
| 0xd7f1…97d8 | Unknown | #51,556,635 | Not stored |
| 0xdede…65d3 | Unknown | #51,556,336 | Not stored |
| 0xd6cb…d526 | Unknown | #51,556,386 | Not stored |
| 0xbb9b…6ce7 | Unknown | #51,556,735 | Not stored |
| 0x118b…55bc | Unknown | #51,556,602 | Not stored |
| 0x8ec1…928d | Unknown | #51,556,751 | Not stored |
| 0x3b39…30ed | Unknown | #51,556,718 | Not stored |
| 0x7698…4677 | Unknown | #51,556,818 | Not stored |
| 0xa478…6c61 | Unknown | #51,556,701 | Not stored |
| 0x90c6…f75b | Unknown | #51,557,200 | Not stored |
| 0xdca7…11e8 | Unknown | #51,556,486 | Not stored |
| 0x8318…d468 | Unknown | #51,556,801 | Not stored |
| 0xfb7b…522c | Unknown | #51,556,649 | Not stored |
| 0xdf8f…bf34 | Unknown | #51,556,784 | Not stored |
| 0xaa66…a007 | Unknown | #51,557,017 | Not stored |
| 0xca23…cff2 | Unknown | #51,556,370 | Not stored |
| 0xc34b…6c9c | Unknown | #51,556,917 | Not stored |
| 0xb118…7525 | Unknown | #51,557,001 | Not stored |
| 0x2cb6…2084 | Unknown | #51,557,117 | Not stored |
| 0x0bbe…8b34 | Unknown | #51,556,967 | Not stored |
| 0x61a1…819f | Unknown | #51,556,984 | Not stored |
| 0xba82…d541 | Unknown | #51,557,133 | Not stored |
| 0x5d34…1aee | Unknown | #51,556,519 | Not stored |
| 0xe110…c00f | Unknown | #51,556,376 | Not stored |
| 0x5e09…0bef | Unknown | #51,556,768 | Not stored |
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 graph28 wallets · 1 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. The first 12 wallets are plotted; every listed wallet can be inspected below.
0x24c14cbd3048dea30f7e3b0d0ce1924a9ca0c1fe
Creator attribution · Major holder
Balance at last observation
2.97%
2026-10-05 22:23:16 UTC · observation, not a live balance
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-05 22:23:28 UTC · Funding research runs only when requested.
Launch activity
Launch exposure, linked wallets and current holdingsHigh Launch-Concentration Signal
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
Wallet activity patterns detected
Launch and wallet-link signals were observed. Shared ownership and creator control are not established by this summary.
Inspect wallet links & supporting evidence▾
- • 1583 wallets acquired in 219 same-block clusters
- • Verified creator wallet currently holds 2.97%
0x24c1…a0c1fe · verified attributionCoverage note: connected-wallet relationships are still loading.
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.