Skip to main content
AVOID.NET
← ORAMAMA Token ($ORAMAMA)reviewed 2026-10-30 · 8 claims checked

Fact-check findings

What an automated fact-checker found when it re-read ORAMAMA Token ($ORAMAMA) 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.

unverifiable

1 claim

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

  1. #5[unverifiable][awaiting moderator]in section: Platform response and account behavior after exposure
    “all of the roughly 11 accounts he identified blocked him on X at approximately the same time shortly after his findings were published”
    reviewerAll accounts blocked ZachXBT at about the same time after publicationA search summary says one report mentions the blocking, but I could not read it. Neither readable cited source mentions it.

partially supported

3 claims

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

  1. #3[partially supported][awaiting moderator]in the timeline
    “Follow-up coverage reported that X appeared to have suspended the identified accounts following ZachXBT's disclosure, a claim attributed to ZachXBT and not independently confirmed by X.”
    reviewerReporting says X appeared to have suspended the identified accounts (attributed to ZachXBT)Source supports the hedged claim. It says 16 accounts, consistent with the page's own note about 10/11/16. The page's attribution to ZachXBT is plausible but not verified; the source does not mention the blocking claim.
  2. #4[partially supported][awaiting moderator]in section: Platform response and account behavior after exposure
    “Coverage also notes that Nikita Bier, X's head of product, was said to be aware of the accounts”
    reviewerNikita Bier was said to be aware of the accountsNeither cited source says Bier was aware of the accounts. Cointelegraph only mentions his general anti-bot announcement. The Coinpedia article could not be read, so the awareness claim is not shown.
  3. #8[partially supported][awaiting moderator]in section: The alleged $ORAMAMA pump-and-dump (February 22, 2026)
    “both carrying only a few thousand dollars of liquidity and flagged as unverified”
    reviewerTwo similarly named Solana tokens, one ORANMAMA/Oran Mama, with few thousand dollars liquidity and unverifiedSolflare shows about $11.2K for ORANMAMA, which is more than 'a few thousand'. Live market figures drift, so this is minor. The ORAMAMA side was not independently checked.

confirmed

2 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: The alleged $ORAMAMA pump-and-dump (February 22, 2026)
    “ZachXBT said on-chain evidence indicated the scheme produced 'six-figure' profits for the operators”
    reviewerA cluster of accounts promoted $ORAMAMA on Feb 22, 2026, with ZachXBT saying on-chain evidence indicated six-figure profitsCore claim matches the thread and Cointelegraph. Page correctly attributes it to ZachXBT.
  2. #2[confirmed][no action needed]in section: Coordinated network and alleged AI-generated fake personas
    “user ID 1804235884826333184”
    reviewerExample account @wanglaurentceo has user ID 1804235884826333184 and was an AI-generated persona based on Mario NawfalUser ID and persona description match the thread. Following count, 17 username changes and 1.8M views not checked (Crypto Times 403, Coinpedia 410).
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.