Skip to main content
AVOID.NET
← PRXVT4 decisions on this page

Audit log

Every state-changing event for PRXVT: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.

  1. #1publishby system:backfill
    2026-05-29 02:35:05Z
    Score: ? → ? (no score change)
    anchoranchored
    chain
    ●mainnet-betaslot 422,848,473
    sig
    5DE5QX1KLoLB…kQAQm4Bnexplorer ↗
    hash
    GM7NepQBUTQ3…wB3WStjWsha256 → base58
    verifying row…full verify ↗
    canonical bytes (5651 B) ▸
    {"actor":"system:backfill","investigation_id":"422ed46b-ac77-43f7-a2f6-63c1fb503dcc","kind":"publish","page_slug":"prxvt","published_at":"2026-05-29T02:35:05.852Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"PRXVT","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.coingecko.com/en/coins/prxvt-by-virtuals","type":"other","url":""},{"credibility":3,"name":"https://basescan.org/token/0xc2ff2e5aa9023b1bb688178a4a547212f4614bc0","type":"other","url":""},{"credibility":3,"name":"https://web3.bitget.com/en/swap/base/0xC2FF2E5aa9023b1bb688178a4a547212f4614bc0","type":"other","url":""},{"credibility":3,"name":"https://messari.io/project/prxvt-by-virtuals","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://github.com/SunWeb3Sec/DeFiHackLabs/blob/main/src/test/2026-01/PRXVT_exp.sol","type":"other","url":""},{"credibility":3,"name":"https://blockthreat.com/blockthreat-week-1-2026/","type":"other","url":""},{"credibility":3,"name":"https://x.com/AndreaPN/status/2006741203480621182","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://x.com/evansWeb3Dev/status/2006732832228471156","type":"other","url":""},{"credibility":3,"name":"https://x.com/ethermage/status/2006940832604237882","type":"other","url":""},{"credibility":3,"name":"https://www.chaincatcher.com/en/article/2160162","type":"other","url":""},{"credibility":3,"name":"https://x.com/AndreaPN/status/2006741203480621182","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://blockthreat.com/blockthreat-week-1-2026/","type":"other","url":""},{"credibility":3,"name":"https://en.wikipedia.org/wiki/ZachXBT","type":"other","url":""},{"credibility":3,"name":"https://x.com/AndreaPN/status/2006741203480621182","type":"other","url":""},{"credibility":3,"name":"https://whitepaper.virtuals.io/info-hub/security/security-audit-reports","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://basescan.org/token/0xc2ff2e5aa9023b1bb688178a4a547212f4614bc0","type":"other","url":""},{"credibility":3,"name":"https://basescan.org/address/0x4b5d32a07b8d3ec5d6928caa30196f8dd6a7c5a9","type":"other","url":""},{"credibility":3,"name":"https://www.coingecko.com/en/coins/prxvt-by-virtuals","type":"other","url":""},{"credibility":3,"name":"https://www.geckoterminal.com/base/pools/0xacad49114f03e0d24bd79abf206ac9523d726fde","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.mexc.com/price/prxvt-by-virtuals/info","type":"other","url":""},{"credibility":3,"name":"https://www.lbank.com/price/prxvt-by-virtuals/what-is","type":"other","url":""},{"credibility":3,"name":"https://holder.io/coins/prxvt/","type":"other","url":""},{"credibility":3,"name":"https://www.coincarp.com/currencies/prxvt-by-virtuals/","type":"other","url":""}]}],"sources_used":[],"summary":"PRXVT (ticker: PRXVT) is a privacy-focused AI-agent token launched on the Base blockchain via the Virtuals Protocol launchpad. The project markets itself as the governance and utility token for px402, an alleged zero-knowledge payment SDK designed to enable anonymous USDC transactions for autonomous AI agents. In early January 2026 the project's staking contract was exploited via a reward-claiming vulnerability, causing the token price to crash to an all-time low and prompting a contested emergency removal of a liquidity pool that was publicly represented as locked for ten years.","timeline":[{"date":"2025-12-01","event":"PRXVT token launches on Base via Virtuals Protocol launchpad, reaching an all-time high of approximately $0.009 during December 2025.","source":""},{"date":"2026-01-01","event":"Suspected Virtuals Protocol address withdraws 4 million VIRTUAL from LP wallet and deposits 1 million VIRTUAL (~$4.07M) into Bybit, per ChainCatcher/Arkham data.","source":""},{"date":"2026-01-05","event":"PRXVT staking contract (stPRXVT) exploited via CREATE2-based reward claim vulnerability. Approximately 32.8 ETH is drained. Token price crashes to an all-time low near $0.000034. Team pauses staking and triggers emergency LP removal.","source":""},{"date":"2026-01-05","event":"PRXVT/VIRTUAL liquidity pool removed from Virtuals Protocol, triggering community debate about the ten-year LP lock guarantee and whether the escape hatch sets a problematic precedent.","source":""},{"date":"2026-01-06","event":"PRXVT team (@PRXVTai) publicly commits to compensate holders affected by the exploit, including users who held leveraged positions via Wasabi Protocol at the time of LP removal.","source":""},{"date":"2026-01-07","event":"BlockThreat Week 1 2026 newsletter catalogues the PRXVT staking exploit alongside other incidents, including Unleash Protocol and Valinity. Full post-mortem details are paywalled.","source":""},{"date":"2026-01-10","event":"DeFiHackLabs publishes a Foundry-based proof-of-concept reproduction of the PRXVT staking exploit (PRXVT_exp.sol) in its 2026-01 directory.","source":""},{"date":"2026-01-01","event":"PRXVT migrates from original token contract (0xc2ff2e5a...) to new contract (0x4b5d32a0...) on Base Mainnet following the exploit.","source":""},{"date":"2026-05-28","event":"PRXVT trading at approximately $0.0018, with a market cap near $1.1 million USD and daily volume near $43,000. ZachXBT flag on the project is noted in AVOID.NET records.","source":""}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 68600a6d-e766-4567-9125-61fa9cb26486
  2. #2rescoreby systemsystem
    2026-10-10 18:45:11Z
    Score: 38 → 51 (+13)
    Rescored under Scoring v2, the published formula (avoid.net/scoring): 38 → 51. Problems weighed by who is responsible: concerns that are not fraud −9.6, incidents the subject suffered −3.2, problems around the subject, caused by others −1.6.
    anchoranchored
    chain
    ●mainnet-betaslot 455,365,009
    sig
    3ugxGhxcqAmp…6dhhPmFxexplorer ↗
    hash
    23uDay7yEYd7…xMqFeWTpsha256 → base58
    verifying row…full verify ↗
    canonical bytes (601 B) ▸
    {"actor":"system","decided_at":"2026-10-10T18:45:11.875Z","decision":"rescore","investigation_id":"422ed46b-ac77-43f7-a2f6-63c1fb503dcc","new_score":51,"page_slug":"prxvt","prev_score":38,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 38 → 51. Problems weighed by who is responsible: concerns that are not fraud −9.6, incidents the subject suffered −3.2, problems around the subject, caused by others −1.6.","score_delta":13,"score_model":"v2","sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 98bbb27e-55ec-4bea-bc6e-4509909aff7a
  3. #3reviewby reviewerreviewer
    2026-10-27 06:46:44Z
    Score: 51 → 51 (no score change)
    The exploit mechanics and 32.8 ETH loss match the DeFiHackLabs PoC. Several claims fail: the ChainCatcher/Arkham VIRTUAL-to-Bybit item is from 2025-01-01, never mentions PRXVT, and is presented as incident-linked on the page. The BlockThreat entry date is wrong (published 2026-01-10) and the exploit date of 2026-01-05 conflicts with BlockThreat's 2026-01-01. The ATH figure is lower than CoinGecko's, and the market snapshot is stale. LP-removal, compensation and ZachXBT claims rest on unreadable X posts or are admitted as unverified. The subject-status search found nothing conclusive.
    anchoranchored
    chain
    ●mainnet-betaslot 461,974,198
    sig
    24LhKeMS97ak…TMKY3CcKexplorer ↗
    hash
    BnhohHQ7SDPf…mLewa6u1sha256 → base58
    verifying row…full verify ↗
    canonical bytes (1470 B) ▸
    {"actor":"reviewer","artifact_identity":"e89450fe461d0219717503da3fbf3326","blocked_count":2,"decided_at":"2026-10-27T06:46:44.357Z","decision":"review","disputed_pct":0.6364,"findings_hash":"BZUC9WXhgoHJxsv1XTEtYQmNPpA1JX4Heu1MDmFWVudu","investigation_id":"422ed46b-ac77-43f7-a2f6-63c1fb503dcc","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"omissions":{"material":0,"total":1},"page_content_hash":"d53b113c99133abd8ad9130b56eeab33e5a84e424987851f51d242e06627af73","page_slug":"prxvt","prev_score":51,"reason":"The exploit mechanics and 32.8 ETH loss match the DeFiHackLabs PoC. Several claims fail: the ChainCatcher/Arkham VIRTUAL-to-Bybit item is from 2025-01-01, never mentions PRXVT, and is presented as incident-linked on the page. The BlockThreat entry date is wrong (published 2026-01-10) and the exploit date of 2026-01-05 conflicts with BlockThreat's 2026-01-01. The ATH figure is lower than CoinGecko's, and the market snapshot is stale. LP-removal, compensation and ZachXBT claims rest on unreadable X posts or are admitted as unverified. The subject-status search found nothing conclusive.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":11,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 2b0d46fb-b887-49a9-a632-5474e56c60dd
  4. #4review denyby judgejudge
    2026-10-27 06:46:44Z
    Score: 51 → 51 (no score change)
    Of 12 claims checked, 2 could not be read because the source blocked the reviewer and were left out of the count. Of the remaining 10, 5 were disputed and 2 could not be verified, giving 70% disputed or unverifiable. The disputed items include a ChainCatcher/Arkham VIRTUAL-to-Bybit transfer that dates from January 2025 and never mentions PRXVT (claim_findings[2] and [3]), an exploit date of 2026-01-05 that conflicts with BlockThreat's 2026-01-01 (claim_findings[5]), a wrong newsletter date (claim_findings[4]) and an understated all-time high (claim_findings[9]). The core exploit mechanics and the 32.8 ETH loss were confirmed (claim_findings[0]), so the penalty sits at the lower end of the band. The ZachXBT flag has no primary source (claim_findings[8]), and the LP-removal and compensation claims rest on X posts that could not be read. The omission and subject-status checks found nothing that changes the band.
    anchoranchored
    chain
    ●mainnet-betaslot 461,974,203
    sig
    o1CxUDQZpiDt…wpoVGaNJexplorer ↗
    hash
    7XTrWjqKPs2S…WSJHcycYsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1595 B) ▸
    {"actor":"judge","artifact_identity":"e89450fe461d0219717503da3fbf3326","band_override":null,"blocked_count":2,"decided_at":"2026-10-27T06:46:44.357Z","decision":"review_deny","delist_requested":true,"disputed_pct":0.6364,"investigation_id":"422ed46b-ac77-43f7-a2f6-63c1fb503dcc","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"page_slug":"prxvt","prev_score":51,"reason":"Of 12 claims checked, 2 could not be read because the source blocked the reviewer and were left out of the count. Of the remaining 10, 5 were disputed and 2 could not be verified, giving 70% disputed or unverifiable. The disputed items include a ChainCatcher/Arkham VIRTUAL-to-Bybit transfer that dates from January 2025 and never mentions PRXVT (claim_findings[2] and [3]), an exploit date of 2026-01-05 that conflicts with BlockThreat's 2026-01-01 (claim_findings[5]), a wrong newsletter date (claim_findings[4]) and an understated all-time high (claim_findings[9]). The core exploit mechanics and the 32.8 ETH loss were confirmed (claim_findings[0]), so the penalty sits at the lower end of the band. The ZachXBT flag has no primary source (claim_findings[8]), and the LP-removal and compensation claims rest on X posts that could not be read. The omission and subject-status checks found nothing that changes the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":11,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 87c512b5-21f1-48ab-95cc-bc48de3a283f
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine — python -m src.verify_decision <event_id>.