Fact-check findings

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

1. #3[disputed][awaiting moderator]in section: Emergency Liquidity Removal and Breach of LP Lock Expectations

   “Independent on-chain data (sourced via Arkham and ChainCatcher) indicated that a suspected Virtuals Protocol address withdrew 4 million VIRTUAL from an LP wallet associated with the incident and subsequently deposited 1 million VIRTUAL (approximately $4.07 million USD at the time) into the Bybit exchange.”

   reviewerChainCatcher/Arkham data show a suspected Virtuals address withdrew 4M VIRTUAL from an LP wallet 'associated with the incident' and deposited 1M VIRTUAL into BybitCited article predates the exploit by a year and never mentions PRXVT, so it cannot be tied to the incident. Correcting this needs editorial judgement: the sentence should be removed or reattributed, not a mechanical text swap. The cited URL itself supports the figures, so I am not proposing a replacement.
   citedwww.chaincatcher.com/en/article/2160162
2. #4[disputed][awaiting moderator]in the timeline

   “Suspected Virtuals Protocol address withdraws 4 million VIRTUAL from LP wallet and deposits 1 million VIRTUAL (~$4.07M) into Bybit, per ChainCatcher/Arkham data.”

   reviewerTimeline: Virtuals address withdrew 4M VIRTUAL and deposited 1M into Bybit in 2026Event is dated 2026 but the source is from 2025-01-01 and does not mention PRXVT. The entry should be removed rather than reworded; no supported replacement text exists.
   citedwww.chaincatcher.com/en/article/2160162
3. #5[disputed][awaiting moderator]in the timeline

   “2026-01-07”

   reviewerBlockThreat Week 1 2026 newsletter catalogued the PRXVT exploit on 2026-01-07Newsletter publication date is 2026-01-10, not 2026-01-07. Note too the newsletter lists the PRXVT incident date as 2026-01-01 with attack vector 'Unknown'.
   Proposed correction (not yet applied)

   2026-01-10
   citedblockthreat.com/blockthreat-week-1-2026/
4. #6[disputed][awaiting moderator]in the timeline

   “2026-01-05”

   reviewerExploit date given as 2026-01-05BlockThreat dates the incident 2026-01-01. The X post IDs cited on the page are consistent with roughly Jan 1-2, 2026 as well. The page's 2026-01-05 is unsourced. Because this value also appears on timeline[3], I did not target that entry separately; verify the LP-removal date independently.
   Proposed correction (not yet applied)

   2026-01-01
5. #10[disputed][awaiting moderator]in section: Project Overview

   “The token's all-time high of approximately $0.009 was reached in December 2025, shortly after launch.”

   reviewerAll-time high about $0.009 reached December 2025CoinGecko ATH is $0.01145, not $0.009. The December timing is not shown by CoinGecko and I could not confirm it. The correction changes only the figure. The page's 'more than 99% drawdown' and '80% decline' figures derive from the $0.009 value and should be rechecked.
   Proposed correction (not yet applied)

   The token's all-time high of approximately $0.01145 was reached in December 2025, shortly after launch.
   citedwww.coingecko.com/en/coins/prxvt-by-virtuals

No source the reviewer could reach confirms or contradicts the claim.

1. #7[unverifiable][awaiting moderator]in section: Emergency Liquidity Removal and Breach of LP Lock Expectations

   “The PRXVT team stated they removed liquidity to prevent the attacker from conducting additional token dumps, and announced that users who held leveraged positions through Wasabi at the time of the LP removal would be compensated.”

   reviewerTeam pauses staking and triggers emergency LP removal; PRXVT team committed to compensate Wasabi leveraged holdersCited only to X posts that could not be read. Searches returned no independent coverage of the compensation pledge.
   citedx.com/AndreaPN/status/2006741203480621182
2. #8[unverifiable][awaiting moderator]in section: Emergency Liquidity Removal and Breach of LP Lock Expectations

   “A developer-researcher posting as @evansWeb3Dev on X noted that this was the first publicly documented instance of a Virtuals LP lock being bypassed and argued the action created a precedent the market had not priced in.”

   reviewerLP removal and the 'first documented bypass' of a Virtuals LP lock, with an escape hatch needing two keysAttributed commentary on X could not be read, and no other reachable source covers it.
   citedx.com/evansWeb3Dev/status/2006732832228471156
3. #9[unverifiable][awaiting moderator]in section: ZachXBT Flag and Community Scrutiny

   “PRXVT has been flagged by ZachXBT, one of the most cited on-chain investigators in the cryptocurrency space, who joined venture firm Paradigm as an incident response advisor in February 2025 and regularly publishes exploit findings via X threads and a Telegram channel.”

   reviewerZachXBT flagged PRXVTThe page itself concedes the flag is unverified. The Wikipedia source cannot support a flag about PRXVT. The headline claim is asserted as fact while the page admits it has no primary source.
   citeden.wikipedia.org/wiki/ZachXBT
4. #13[unverifiable][awaiting moderator]in section: ZachXBT Flag and Community Scrutiny

   “which were audited by PeckShield in March and October 2024”

   reviewerVirtuals base contracts audited by PeckShield in March and October 2024; no audit of staking contractI did not fetch the Virtuals audit page, so the audit dates and the absence of a staking audit are unchecked.
   citedwhitepaper.virtuals.io/info-hub/security…ty-audit-reports

The claim was accurate when written but events since have overtaken it.

1. #11[stale][awaiting moderator]in section: Project Overview

   “As of late May 2026, approximately 624 million tokens were in circulation with a market capitalization near $1.1 million USD.”

   reviewerAs of late May 2026 about 624M circulating, market cap near $1.1M, price about $0.0018, volume about $43,000Point-in-time market data is dated and current CoinGecko figures differ materially. Not edited because the May figure may have been accurate then; marked stale, with no replacement proposed as a snapshot is volatile.
   citedwww.coingecko.com/en/coins/prxvt-by-virtuals

The cited evidence supports part of the claim but not all of it.

1. #2[partially supported][awaiting moderator]in section: Staking Contract Exploit (January 2026)

   “The vulnerability lay in how the stPRXVT contract calculated earned amounts: it failed to account for reward claims made via contract-instantiation patterns, allowing the attacker to drain reward pools repeatedly.”

   reviewerThe page's root-cause explanation of the vulnerabilityMechanism is consistent with the PoC, but the stated root cause is presented as fact without a source.
   citedgithub.com/SunWeb3Sec/DeFiHackLabs/blob/…01/PRXVT_exp.sol

The cited evidence supports the claim as written.

1. #1[confirmed][no action needed]in section: Staking Contract Exploit (January 2026)

   “Total losses were recorded at approximately 32.8 ETH.”

   reviewerStaking contract exploit lost about 32.8 ETH; attacker spent ~1 ETH, staked 400,000 PRXVT, used CREATE2 contracts; addresses as listedPoC matches amounts and addresses. The PoC does not explain the root cause, so the page's explanation of the flaw is inference.
   citedgithub.com/SunWeb3Sec/DeFiHackLabs/blob/…01/PRXVT_exp.sol
2. #12[confirmed][no action needed]in section: Project Overview

   “Total maximum supply is 1,000,000,000 PRXVT.”

   reviewerToken and staking contract addresses, ERC-20 on Base, 1B max supplySupply confirmed. I did not independently confirm the migrated-contract claim or the audit-absence claims.
   citedwww.coingecko.com/en/coins/prxvt-by-virtuals