Virtuals Protocol (VIRTUAL)
0x8c4252c87081c88c6ad57d6dd97e1cafebf842b7Scan results are a snapshot. Select Analyze Again to run a new scan.
5 of 7 analysis modules returned usable evidence on Arc. Some checks remain incomplete. Confirmed risk findings still apply; missing evidence does not establish safety.
Required native contract evidence could not be fully verified
LP lock status could not be determined from available data
Verified below: market observation (Market provider not recorded), ERC-20 metadata, total supply, contract bytecode, proxy slot, owner, deployer.
High Risk
The published assessment requires holder-concentration recomputation. Displayed figures use the current account-role evidence rules; independent account control remains unverified. Other recorded risks remain applicable.
Scanned at 2026-10-09 14:41:38 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 (10): 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.
- High-Priority Risk
1. Unclassified Contract Concentration
An unclassified contract holds 76.19% of supply.
- Risk Indicator
2. Contract Security
Owner can mint new supply.
Why it matters: Contract privileges or transfer rules can change trading conditions. Review the verified capability and its limitations.
Bottom line
The published assessment requires holder-concentration recomputation. Displayed figures use the current account-role evidence rules; independent account control remains unverified. Other recorded risks remain applicable.
Biggest concerns
holder concentration · contract controls
Evidence & Caveats 2 recorded reasons · 10 verification gapsClick to expandExpanded
Recorded verdict explanation
The published assessment requires holder-concentration recomputation. Displayed figures use the current account-role evidence rules; independent account control remains unverified. Other recorded risks remain applicable.
Some checks unverified: Token controls unverified · Contract Holder Unclassified · LP protection unverified · Evidence needs refreshing · Holder evidence incomplete.
1. Unclassified Contract Concentration · High
An unclassified contract holds 76.19% of supply. Its purpose and control remain unverified.
2. Contract Security · Medium
Owner can mint new supply.
Why it matters: Contract privileges or transfer rules can change trading conditions. Review the verified capability and its limitations.
Evidence quality & missing verification
Data available: 5/7 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
- 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 76.19% of supply. Its purpose and control remain unverified.
Ruggy commentary
“Serious problems here. Do not treat this as a normal token.”
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
$538,546.92
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: 97.1% · 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
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 76.19% of supply. Its purpose and control remain unverified. Currently sits at $538.5K in liquidity, $62.1K traded in the last 24h, 290 holders. The identified creator wallet holds less than 1% of supply, but total team or connected-wallet ownership is not established.
Why this verdict?▾
- + High riskUnclassified Contract ConcentrationAn unclassified contract holds 76.19% of supply. Its purpose and control remain unverified.
- + ConcernContract SecurityOwner can mint new supply.
- NeutralLiquidityLiquidity depth looks reasonable ($538,547).
- NeutralProject LifecycleProject is actively trading on-chain.
- NeutralLargest Holder AccountLargest sampled holder account holds 76.19%; independent control is unverified.
- NeutralSampled Holder Accounts10 sampled accounts hold 97.06% in total; this is a lower bound when the filtered sample has fewer than ten accounts.
Key Findings
🔴 High RiskAn unclassified contract holds 76.19% of supply.
Independent control and purpose remain unverified.
- Owner can mint additional supply.
Liquidity protection is unverified.
Liquidity protection is unverified. No verified locked or burned LP position was established.
- Liquidity depth looks reasonable.
Show all 5 findings
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.
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
- 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
0x271d…b55a · 0.00% current measured holdings
Attribution: rpc-creation-trace. Identified wallet only; this does not establish total team ownership.
Deployment receipt: 0x0990…d187
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.
0x271dfca79d01b0ba17ec4eccfb4cc88dec48b55a
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-09 14:41:38 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.
No additional creator signals were reported.
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%
0x271d…48b55a · 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
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.
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.
