Skip to main content
AVOID.NET
← HNUT (Holly The Squirrel) Solana Meme Coinreviewed 2026-10-27 · 11 claims checked

Fact-check findings

What an automated fact-checker found when it re-read HNUT (Holly The Squirrel) Solana Meme Coin against the sources the page cites. Only the most recent review is shown.

Read this first

These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.

“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.

Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.

disputed

3 claims

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. #1[disputed][awaiting moderator]in the summary
    “Blockchain security firm PeckShield flagged roughly 78% of early trading volume as bundled transactions”
    reviewerPeckShield flagged roughly 78% of early trading volume as bundled transactionsThe 78% figure is attributed to unnamed reports, not PeckShield. The page repeats the misattribution in the summary, section 2 and timeline[2].
    Proposed correction (not yet applied)
    Reports cited by Yahoo Finance and BitRss state that roughly 78% of early trading volume involved bundled transactions; PeckShield's own post cited only the 99% price drop
  2. #2[disputed][awaiting moderator]in section: PeckShield Alert and Bundled Transaction Analysis
    “PeckShield's on-chain analysis indicated that roughly 78% of early trading activity involved bundled transactions”
    reviewerPeckShield's on-chain analysis indicated 78% bundledSame misattribution as in the summary.
    Proposed correction (not yet applied)
    Reports accompanying PeckShield's alert indicated that roughly 78% of early trading activity involved bundled transactions
  3. #3[disputed][awaiting moderator]in the timeline
    “PeckShield stated roughly 78% of early trading volume involved bundled transactions consistent with insider supply concentration.”
    reviewerTimeline: PeckShield stated 78% bundledSame misattribution.
    Proposed correction (not yet applied)
    Accompanying reports stated roughly 78% of early trading volume involved bundled transactions, a pattern associated with insider supply concentration.

unverifiable

1 claim

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

  1. #11[unverifiable][awaiting moderator]in section: Pump.fun Platform Context
    “In January 2025, a lawsuit was filed against Pump.fun alleging it exploited users with offensive content, according to The Crypto Basic.”
    reviewerJanuary 2025 lawsuit against Pump.funNot fetched. The URL slug and date are consistent with the claim, but I did not read the article. The lawsuit is tangential, and the page's wording is a paraphrase of the headline.

partially supported

2 claims

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

  1. #4[partially supported][awaiting moderator]in section: Post-Collapse Market State
    “The token price had fallen from a high near $0.055–$0.07 (figures varied by source and measurement timing) to effectively zero.”
    reviewerPrice fell from a high near $0.055-$0.07The collapse-source figure is $0.007, an order of magnitude below the page's range. The $0.07 figure was not found in any fetched source. The $0.055 figure is from the surge reporting.
  2. #9[partially supported][awaiting moderator]in section: Secondary Phishing Activity
    “multiple community trackers and news aggregators reported the emergence of phishing-style accounts on X (formerly Twitter) impersonating recovery tools or airdrop claim links targeting traders who had lost funds.”
    reviewerPhishing accounts on X impersonating recovery tools or airdrop claim linksSupported in substance. 'News aggregators' is an extra attribution, and the same-day timeline[3] date is inferred.

confirmed

5 claims

The cited evidence supports the claim as written.

  1. #5[confirmed][no action needed]in section: Price Surge and Pre-Collapse Warnings
    “On or around December 30, 2025, HNUT recorded a 24-hour price gain of approximately 703%, reaching a reported peak price of $0.055 and a market capitalization of roughly $55 million according to KuCoin and ChainCatcher.”
    reviewer703% 24h gain, $0.055, $55M market cap, third in volume (KuCoin)Figures match. The $70.94M Bitget figure was not separately fetched.
  2. #6[confirmed][no action needed]in section: Price Surge and Pre-Collapse Warnings
    “Crypto Scam Hunter reportedly issued a warning flagging coordinated transfers from multiple wallets into a single address”
    reviewerCrypto Scam Hunter warning on Dec 29 flagged coordinated transfersSupported by BitRss. The KuCoin article does not mention Crypto Scam Hunter.
  3. #7[confirmed][no action needed]in section: Post-Collapse Market State
    “HNUT's remaining liquidity was reported at approximately $29,000 and its market capitalization at under $1,400”
    reviewerRemaining liquidity about $29,000 and market cap under $1,400Matches Yahoo and BitRss.
  4. #8[confirmed][no action needed]in section: Post-Collapse Market State
    “One anecdotal report cited by BitRss described a trader who allegedly entered a position at $2,300 and held a notional value of $3.1 million before the collapse”
    reviewerTrader entered at $2,300 and held $3.1MAccurately flagged as unverified.
  5. #10[confirmed][no action needed]in section: Regulatory and Legal Status
    “no regulatory action by the SEC, CFTC, DOJ, or any equivalent authority has been publicly reported in connection with HNUT or its launch.”
    reviewerNo regulatory action reported; developers unidentifiedSearches found no regulatory action or developer identification. This is an absence claim, so it is supported only weakly.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.