RUG.TOOLS
NIGHT (NIGHT)
0xfe930c2d63aed9b82fc4dbc801920dd2c1a3224fScan results are a snapshot. Select Analyze Again to run a new scan.
4 of 8 analysis modules returned usable evidence on BNB Chain. 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
Liquidity protection is unverified. Position-lock checks are not available for this pool; this verdict does not establish that its liquidity is protected.
Liquidity depth could not be verified
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-07 07:30:44 UTC
Market conditions can change after a scan. Select Analyze Again to refresh.
Token controls unverified · LP protection unverified · Evidence needs refreshing.
Verification gaps (9): 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: Required native contract evidence could not be fully verified · 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. Largest Holder Account
one holder account holds 38.0% of supply.
- Risk Indicator
3. Sampled Holder Accounts
sampled holder accounts hold 89.4% — high concentration.
- Risk Indicator
4. Creator History
Creator has a concerning launch history.
Why it matters: Creator holdings or capabilities are worth monitoring, but do not by themselves establish intent or future trades.
Bottom line
The contract behaves like a honeypot — buyers cannot exit. Do not trade.
Biggest concerns
contract controls · holder concentration
Evidence & Caveats 4 recorded reasons · 9 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.
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. Largest Holder Account · Medium
one holder account holds 38.0% of supply.
3. Sampled Holder Accounts · Medium
sampled holder accounts hold 89.4% — high concentration.
4. Creator History · Medium
Creator has a concerning launch history.
Why it matters: Creator holdings or capabilities are worth monitoring, but do not by themselves establish intent or future trades.
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.
- On-Chain Contract Checks: Required native contract evidence could not be fully verified
- Market data (DexScreener): No active market pair verified
- LP ownership: Liquidity protection is unverified. Position-lock checks are not available for this pool; this verdict does not establish that its liquidity is protected.
- Liquidity depth: Liquidity depth could not be verified
- critical contract-security fields are unknown
- liquidity protection cannot be evaluated on this chain
- the underlying evidence is stale and has not been re-verified
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. Position-lock checks are not available for this pool; this verdict does not establish that its liquidity is protected.
Market snapshot & additional signals
Market snapshot & key evidence
Total tracked liquidity
$83,857.21
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. Earlier or mixed market observations are being retained.
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: 89.4% · 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.
Liquidity depth looks reasonable, however honeypot detected — cannot sell after buying. Currently sits at $83.9K in liquidity, $95.3K traded in the last 24h, 15.6K holders. The largest wallet controls 38.0% of supply. The identified creator wallet holds less than 1% of supply, but total team or connected-wallet ownership is not established.
Why this verdict?▾
- Critical overrideContract SecurityHoneypot — buyers cannot sell.
- + ConcernLargest Holder Accountone holder account holds 38.0% of supply.
- + ConcernSampled Holder Accountssampled holder accounts hold 89.4% — high concentration.
- + ConcernCreator HistoryCreator has a concerning launch history.
- NeutralLiquidityLiquidity depth looks reasonable ($83,857).
- NeutralProject LifecycleProject is actively trading on-chain.
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.
Single wallet holds 38.0% of supply.
One wallet controlling a quarter of supply can crash the price on exit.
- Owner can mint additional supply.
Show all 7 findings
- Ownership can be reclaimed after renouncement.
- Liquidity depth looks reasonable.
Identified creator wallet currently holds 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
- 0.00%
- 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.
Creator provenance
0x2fb4…5200 · 0.00% current measured holdings
Attribution: rpc-creation-trace. Identified wallet only; this does not establish total team ownership.
Deployment receipt: 0xb673…b840
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 graph11 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.
0x2fb4d46372ea1748ec3c29bd2c7b536019df5200
Creator attribution
Balance at last observation
Unknown
Time unavailable · 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.
Enhanced funding history is unavailable on this chain or snapshot. The saved report remains available above.
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-07 07:30:44 UTC · Funding research runs only when requested.
Launch activity
Launch exposure, linked wallets and current holdingsNo launch-window Transfer logs were returned; launch exposure could not be verified Missing launch evidence is never interpreted as a clean or low-risk result.
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▾
- • Verified creator wallet currently holds 0.00%
0x2fb4…df5200 · verified attributionCoverage note: No launch-window Transfer logs were returned; launch exposure could not be verified; 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
Concentrated-liquidity position ownership and lock protection have not been verified. No protective claim is made without position evidence.
Protection applies only to the measured pool or position; it does not establish overall token safety.
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.
Launch history: No launch-window Transfer logs were returned; launch exposure could not be verified. Missing extended evidence is never interpreted as a clean signal.