← Nina/Mo3 decisions on this page
Audit log
Every state-changing event for Nina/Mo: 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.
- #1publishby system:backfill2026-05-30 13:03:47ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 423,161,781
- sig
JyqCBghfc36o…SWCcjbpuexplorer ↗- hash
5WKUnQsyKeHx…ArZD4NJ7sha256 → base58
verifying row…full verify ↗canonical bytes (8828 B) ▸
{"actor":"system:backfill","investigation_id":"6e0d7808-17b4-4d32-be8a-b8698920809c","kind":"publish","page_slug":"ninamo","published_at":"2026-05-30T13:03:47.131Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Nina/Mo","sections":[{"content":"So far there's multiple suspects in the [$330M (3520 BTC)](https://x.com/zachxbt/status/1916756932763046273) social engineering theft from April 27, 2025. Both have since deleted social media accounts.\n\n-Nina/Mo: Operates a call scam centre in Camden, UK \n-W0rk: Assisted with the site/call","heading":"Nina/Mo","severity":"critical","sources":[{"credibility":2,"name":"Nina/Mo","type":"social_media","url":"https://t.me/zachxbt/244"}]},{"body":"The name 'Ninamo' was submitted to AVOID.NET for investigation as a potential crypto entity. Searches were conducted across major cryptocurrency tracking platforms including CoinGecko, CoinMarketCap, CoinLore, and LiveCoinWatch, as well as blockchain explorers including Etherscan, BscScan, and Solscan. No token, protocol, exchange, or project operating under the exact name 'Ninamo' was found on any of these platforms. Similar-sounding projects that returned in searches — including Ninneko (NINO), NIMO Protocol (NIM), Nomina (NOM), and NinaPumps (NINA) — are distinct entities unrelated to the submitted name. The Wayback Machine (web.archive.org) showed no archived snapshots for ninamo.com, ninamo.io, ninamo.xyz, ninamo.net, ninamo.org, or ninamo.app. No active or historical website associated with this name could be confirmed. The Twitter handle @Ninamo_lcr exists but relates to an individual artist account with no crypto-related content. Without a verifiable entity to investigate, all findings in this report carry extremely low confidence and should be treated accordingly.","severity":"low","sources":[{"credibility":2,"name":"CoinGecko — no 'Ninamo' listing found","type":"other","url":"https://www.coingecko.com/en/coins"},{"credibility":2,"name":"CoinMarketCap — no 'Ninamo' listing found","type":"other","url":"https://coinmarketcap.com/"},{"credibility":1,"name":"California DFPI Crypto Scam Tracker — no 'Ninamo' entry found","type":"regulatory","url":"https://dfpi.ca.gov/consumers/crypto/crypto-scam-tracker/"}],"title":"Entity Identification"},{"body":"The California Department of Financial Protection and Innovation (DFPI) Crypto Scam Tracker, one of the most comprehensive public databases of reported crypto fraud in the United States, was searched for 'Ninamo' and returned no matching entries. The FBI's Internet Crime Complaint Center (IC3), the FTC's consumer complaint portal, and CFTC and SEC enforcement action databases were also searched, with no results for an entity named Ninamo. The Comparitech worldwide crypto and NFT scam tracker, which aggregates community-reported fraud incidents, similarly returned no entries. Given the absence of any record across these high-credibility databases, it is not possible to confirm allegations of fraud, a rug pull, or any other specific misconduct at this time. This absence of evidence does not constitute evidence of legitimacy — unverified or newly emerged entities may not yet appear in public databases even if problematic activity is occurring. Any future complaints or reports linked to a 'Ninamo' entity should be documented and tracked as they emerge.","severity":"medium","sources":[{"credibility":1,"name":"FBI Internet Crime Complaint Center — Cryptocurrency Fraud Information","type":"regulatory","url":"https://www.ic3.gov/CrimeInfo/Cryptocurrency"},{"credibility":1,"name":"California DFPI Crypto Scam Tracker","type":"regulatory","url":"https://dfpi.ca.gov/consumers/crypto/crypto-scam-tracker/"},{"credibility":2,"name":"Comparitech Worldwide Crypto and NFT Rug Pulls and Scams Tracker","type":"research","url":"https://www.comparitech.com/crypto/cryptocurrency-scams/"},{"credibility":1,"name":"SEC Enforcement Actions — no Ninamo results","type":"regulatory","url":"https://www.sec.gov/submit-tip-or-complaint/report-problem-investment-account-or-financial-professional"},{"credibility":1,"name":"CFTC Enforcement Actions database — no Ninamo results","type":"regulatory","url":"https://www.cftc.gov/LawRegulation/EnforcementActions/index.htm"}],"title":"Scam and Fraud Database Search Results"},{"body":"Searches across blockchain explorers and on-chain analytics platforms returned no wallet addresses, contract addresses, or transaction histories attributable to an entity named Ninamo. No Ethereum (ERC-20), BNB Chain (BEP-20), Solana SPL token, or Bitcoin address could be verified as associated with this name. Without a confirmed on-chain presence, it is not possible to assess fund flows, liquidity events, or treasury movements. If a 'Ninamo' token or smart contract is deployed in the future, on-chain analysis using tools such as Etherscan, BscScan, Dune Analytics, or Chainalysis would be the appropriate next step for tracing any alleged misconduct.","severity":"low","sources":[{"credibility":2,"name":"BscScan BEP-20 Token Explorer — no Ninamo contract found","type":"on_chain","url":"https://bscscan.com/token/"},{"credibility":2,"name":"DexCheck AI Wallet Analyzer","type":"on_chain","url":"https://dexcheck.ai/app/wallet-analyzer"}],"title":"Wallet and Contract Address Research"}],"sources_used":[{"archive_timestamp":null,"archive_url":null,"credibility":2,"name":"Nina/Mo","type":"social_media","url":"https://t.me/zachxbt/244"},{"archive_timestamp":null,"archive_url":null,"credibility":2,"name":"CoinGecko cryptocurrency database","type":"other","url":"https://www.coingecko.com/en/coins"},{"archive_timestamp":"2026-05-24T21:43:20+00:00","archive_url":"http://web.archive.org/web/20260524214320/https://coinmarketcap.com/","credibility":2,"name":"CoinMarketCap cryptocurrency database","type":"other","url":"https://coinmarketcap.com/"},{"archive_timestamp":null,"archive_url":null,"credibility":1,"name":"California DFPI Crypto Scam Tracker","type":"regulatory","url":"https://dfpi.ca.gov/consumers/crypto/crypto-scam-tracker/"},{"archive_timestamp":null,"archive_url":null,"credibility":1,"name":"FBI IC3 Cryptocurrency Fraud Information","type":"regulatory","url":"https://www.ic3.gov/CrimeInfo/Cryptocurrency"},{"archive_timestamp":null,"archive_url":null,"credibility":2,"name":"Comparitech Worldwide Crypto and NFT Scam Tracker","type":"research","url":"https://www.comparitech.com/crypto/cryptocurrency-scams/"},{"archive_timestamp":"2026-04-20T23:24:30+00:00","archive_url":"http://web.archive.org/web/20260420232430/https://www.cftc.gov/LawRegulation/EnforcementActions/index.htm","credibility":1,"name":"CFTC Enforcement Actions","type":"regulatory","url":"https://www.cftc.gov/LawRegulation/EnforcementActions/index.htm"},{"archive_timestamp":"2026-03-01T16:45:55+00:00","archive_url":"http://web.archive.org/web/20260301164555/https://www.sec.gov/submit-tip-or-complaint/report-problem-investment-account-or-financial-professional","credibility":1,"name":"SEC Investor Complaint Portal","type":"regulatory","url":"https://www.sec.gov/submit-tip-or-complaint/report-problem-investment-account-or-financial-professional"},{"archive_timestamp":"2026-05-26T03:35:24+00:00","archive_url":"https://web.archive.org/web/20260526033524/https://bscscan.com/tokens","credibility":2,"name":"BscScan BEP-20 Token Explorer","type":"on_chain","url":"https://bscscan.com/token/"},{"archive_timestamp":"2026-03-01T08:14:51+00:00","archive_url":"http://web.archive.org/web/20260301081451/https://dexcheck.ai/app/wallet-analyzer","credibility":2,"name":"DexCheck AI Wallet Analyzer","type":"on_chain","url":"https://dexcheck.ai/app/wallet-analyzer"},{"archive_timestamp":null,"archive_url":null,"credibility":3,"name":"Twitter — @Ninamo_lcr (artist account, not crypto-related)","type":"social_media","url":"https://twitter.com/ninamo_lcr"}],"summary":"Ninamo is a purported crypto entity whose name was submitted for investigation on AVOID.NET. Exhaustive searches across regulatory databases, blockchain explorers, crypto news outlets, scam trackers, social media platforms, domain registries, and the Wayback Machine returned no verifiable information about any crypto project, exchange, token, or DeFi protocol operating under the name Ninamo. No wallet addresses, enforcement actions, community reports, or archived web presence could be located.","timeline":[{"date":"2025-05-02","event":"Nina/Mo","source":"t.me","source_url":"https://t.me/zachxbt/244"},{"date":"2026-05-15","event":"AVOID.NET investigation initiated for entity named 'Ninamo'. Exhaustive multi-source search returned no verifiable information about any crypto project, exchange, token, or platform operating under this name.","source":"AVOID.NET internal investigation","source_url":"https://avoid.net"}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision 5a57f9b1-f06b-4c32-9830-23b5592b408f - #2reviewby reviewerreviewer2026-06-03 02:53:59ZScore: 83 → 83 (no score change)The page contains one factual date error (theft date stated as April 27 vs the confirmed April 28, 2025) and several source mischaracterizations where informational pages are described as searchable complaint databases. The core identification of Nina/Mo and W0rk as suspects named by ZachXBT is supported by multiple independent corroborating sources. The most significant finding is a structural incoherence: the summary and three sections treat 'Ninamo' as an unverifiable crypto entity with no presence, while Section 1 concerns a real named suspect in one of the largest recorded Bitcoin thefts. The page requires restructuring to match its actual subject.anchoranchored
- chain
- ●mainnet-betaslot 423,940,086
- sig
ARWPXXmiD6oG…2BP6kngMexplorer ↗- hash
AwFAEZMiCcY7…S3m8WAN9sha256 → base58
verifying row…full verify ↗canonical bytes (1003 B) ▸
{"actor":"reviewer","decided_at":"2026-06-03T02:53:59.156Z","decision":"review","investigation_id":"6e0d7808-17b4-4d32-be8a-b8698920809c","new_score":83,"page_slug":"ninamo","prev_score":83,"reason":"The page contains one factual date error (theft date stated as April 27 vs the confirmed April 28, 2025) and several source mischaracterizations where informational pages are described as searchable complaint databases. The core identification of Nina/Mo and W0rk as suspects named by ZachXBT is supported by multiple independent corroborating sources. The most significant finding is a structural incoherence: the summary and three sections treat 'Ninamo' as an unverifiable crypto entity with no presence, while Section 1 concerns a real named suspect in one of the largest recorded Bitcoin thefts. The page requires restructuring to match its actual subject.","score_delta":0,"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 87ba1180-e3b4-4797-8187-6c99ef6fc2a5 - #3review reviseby judgejudge2026-06-03 02:53:59ZScore: 83 → 71 (-12)The reviewer's stated disputed_pct of 25% places this page in the review_revise band. The single directly disputed claim (claim_findings[0]: theft date April 27 vs confirmed April 28) is a minor peripheral error rather than a core allegation failure. However, four high-priority coverage gaps — most critically the structural incoherence gap flagging that the page is formatted as a crypto-token investigation while its actual subject is a named individual suspect in a major Bitcoin theft — substantially increase the revision weight. Additionally, claim_findings[9] and claim_findings[6] identify source mischaracterizations where informational pages (IC3, SEC tip portal) are presented as searchable enforcement databases, which is a credibility issue for the methodology sections. The core identification of Nina/Mo and W0rk as suspects (claim_findings[1-4]) is confirmed by multiple independent Tier 1 and Tier 2 sources and does not require revision. The page's summary and Sections 2-4 need to be restructured to reflect the actual investigation subject.anchoranchored
- chain
- ●mainnet-betaslot 423,940,089
- sig
3qvujoyM9vNF…YuueKuMCexplorer ↗- hash
GPDn5QEpUtvp…hx1vUcjasha256 → base58
verifying row…full verify ↗canonical bytes (1409 B) ▸
{"actor":"judge","decided_at":"2026-06-03T02:53:59.156Z","decision":"review_revise","investigation_id":"6e0d7808-17b4-4d32-be8a-b8698920809c","new_score":71,"page_slug":"ninamo","prev_score":83,"reason":"The reviewer's stated disputed_pct of 25% places this page in the review_revise band. The single directly disputed claim (claim_findings[0]: theft date April 27 vs confirmed April 28) is a minor peripheral error rather than a core allegation failure. However, four high-priority coverage gaps — most critically the structural incoherence gap flagging that the page is formatted as a crypto-token investigation while its actual subject is a named individual suspect in a major Bitcoin theft — substantially increase the revision weight. Additionally, claim_findings[9] and claim_findings[6] identify source mischaracterizations where informational pages (IC3, SEC tip portal) are presented as searchable enforcement databases, which is a credibility issue for the methodology sections. The core identification of Nina/Mo and W0rk as suspects (claim_findings[1-4]) is confirmed by multiple independent Tier 1 and Tier 2 sources and does not require revision. The page's summary and Sections 2-4 need to be restructured to reflect the actual investigation subject.","score_delta":-12,"sequence_num":3,"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 addc62ee-92c2-4af0-8ca1-b8b7617c4bf9
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>.