Skip to main content
AVOID.NET
← Nemo Yield Trading5 decisions on this page

Audit log

Every state-changing event for Nemo Yield Trading: 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-26 18:30:21Z
    Score: ? → ? (no score change)
    anchoranchored
    chain
    ●mainnet-betaslot 422,338,837
    sig
    cPkfxjfwH3QM…zAqoVgaNexplorer ↗
    hash
    Cj6WvPh1cpFE…Ntx7Eo9msha256 → base58
    verifying row…full verify ↗
    canonical bytes (5643 B) ▸
    {"actor":"system:backfill","investigation_id":"20f595cd-4fa0-459f-930f-f424155f06bd","kind":"publish","page_slug":"nemo-yield-trading","published_at":"2026-05-26T18:30:21.862Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Nemo Yield Trading","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://defillama.com/protocol/nemo-yield-trading","type":"other","url":""},{"credibility":3,"name":"https://iq.wiki/wiki/nemo-protocol","type":"other","url":""},{"credibility":3,"name":"https://www.rootdata.com/Projects/detail/Nemo%20Protocol?k=MTM5NTE%3D","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.coindesk.com/markets/2025/09/08/sui-based-yield-protocol-nemo-exploited-for-usd2-4m-in-usdc","type":"other","url":""},{"credibility":3,"name":"https://finance.yahoo.com/news/nemo-protocol-hacked-2-4m-081422991.html","type":"other","url":""},{"credibility":3,"name":"https://www.theblock.co/post/369766/sui-nemo-protocol-exploit","type":"other","url":""},{"credibility":3,"name":"https://crypto.news/nemo-protocol-2-6m-exploit-caused-by-developers-unaudited-code/","type":"other","url":""},{"credibility":3,"name":"https://coinfomania.com/nemo-protocol-exploit-steals-2-4-million-and-tests-defi-security/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://cointelegraph.com/news/2-6-million-lost-in-nemo-hack-due-to-unaudited-code-and-ignored-vulnerability","type":"other","url":""},{"credibility":3,"name":"https://www.theblock.co/post/370273/nemo-protocol-unaudited-code-exploit","type":"other","url":""},{"credibility":3,"name":"https://cryptonews.com/news/nemo-protocol-blames-2-6m-exploit-on-developer-who-deployed-unaudited-code/","type":"other","url":""},{"credibility":3,"name":"https://bitcoinethereumnews.com/tech/auditor-flagged-issue-before-2-59m-nemo-hack-team-admits/","type":"other","url":""},{"credibility":3,"name":"https://finance.yahoo.com/news/nemo-protocol-blames-2-6m-083310308.html","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://cryptonews.com/news/nemo-protocol-issues-neom-debt-tokens-to-compensate-2-6m-exploit-victims/","type":"other","url":""},{"credibility":3,"name":"https://www.theblock.co/post/370581/nemo-protocol-debt-token-program-exploit","type":"other","url":""},{"credibility":3,"name":"https://www.cryptopolitan.com/nemo-protocol-debt-token-program-hack-victim/","type":"other","url":""},{"credibility":3,"name":"https://crypto.news/nemo-protocol-to-issue-debt-token-to-compensate-2-6m-hack-victims/","type":"other","url":""},{"credibility":3,"name":"https://coinpedia.org/news/nemo-protocol-introduces-neom-token-to-compensate-2-4m-hack-losses/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://defillama.com/protocol/nemo-yield-trading","type":"other","url":""},{"credibility":3,"name":"https://www.coindesk.com/markets/2025/09/08/sui-based-yield-protocol-nemo-exploited-for-usd2-4m-in-usdc","type":"other","url":""},{"credibility":3,"name":"https://x.com/SmartDropFarmer/status/1998698715125571968","type":"other","url":""}]}],"sources_used":[],"summary":"Nemo Protocol is a Sui-based DeFi yield trading platform that suffered a $2.6 million exploit on September 7, 2025, caused by an unnamed developer who deployed unaudited code to mainnet while bypassing internal review processes. A security auditor had flagged a related vulnerability 27 days before the attack, which the team acknowledged it failed to address in time. The protocol's TVL has since collapsed to zero and it has been flagged as high-risk by trust intelligence sources.","timeline":[{"date":"2022-06","event":"Nemo Protocol's official X account established; project founded.","source":""},{"date":"2025-01","event":"Developer submits code to MoveBit auditors without disclosing new unaudited features mixed into the submission. Protocol completes Sui Hydropower Accelerator first cohort.","source":""},{"date":"2025-08-11","event":"Security firm Asymptotic issues a C-2 severity warning flagging a vulnerability in Nemo's contract code that allows unauthorized state modification. The developer allegedly dismisses the severity and no fix is deployed.","source":""},{"date":"2025-09-07","event":"Exploit occurs at approximately 16:00 UTC. Attacker uses exposed flash loan function combined with flawed query function to drain approximately $2.4-2.6 million from the SY/PT liquidity pool. Stolen assets bridged to Ethereum via Wormhole CCTP. TVL collapses from $6.3M to $1.57M.","source":""},{"date":"2025-09-08","event":"PeckShield publicly flags the breach. Nemo Protocol confirms the attack and announces protocol pause. Nemo offers a 10% white-hat bounty to the attacker.","source":""},{"date":"2025-09-11","event":"Nemo Protocol releases post-mortem report, attributing the exploit to unaudited code deployed by an internal developer via single-signature address, and admitting the Asymptotic warning was not adequately addressed.","source":""},{"date":"2025-09-14","event":"Nemo Protocol announces the NEOM debt token compensation program, issuing one NEOM per dollar lost. Team acknowledges it lacks capital for direct USD reimbursement.","source":""},{"date":"2026-05","event":"Social media reports indicate the vault migration was completed and NEOM tokens are claimable. NEOM reportedly trades below its $1.00 peg. Protocol TVL remains at zero.","source":""}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision a54aa4e7-8a26-4d2f-a299-c2c061b9f0c7
  2. #2rescoreby systemsystem
    2026-10-10 18:44:39Z
    Score: 28 → 60 (+32)
    Rescored under Scoring v2, the published formula (avoid.net/scoring): 28 → 60. Problems weighed by who is responsible: concerns that are not fraud −6.4, incidents the subject suffered −3.2, problems around the subject, caused by others −1.6; legitimacy credit long-running +6.
    anchoranchored
    chain
    ●mainnet-betaslot 455,364,429
    sig
    8eD4m6bUZvZc…PKu2QGdNexplorer ↗
    hash
    5U3coXnKYtxM…4PL3jFqcsha256 → base58
    verifying row…full verify ↗
    canonical bytes (649 B) ▸
    {"actor":"system","decided_at":"2026-10-10T18:44:39.601Z","decision":"rescore","investigation_id":"20f595cd-4fa0-459f-930f-f424155f06bd","new_score":60,"page_slug":"nemo-yield-trading","prev_score":28,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 28 → 60. Problems weighed by who is responsible: concerns that are not fraud −6.4, incidents the subject suffered −3.2, problems around the subject, caused by others −1.6; legitimacy credit long-running +6.","score_delta":32,"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 8ea357eb-d51b-4724-ae06-165ea7890c3a
  3. #3reviewby reviewerreviewer
    2026-11-03 23:36:16Z
    Score: 60 → 60 (no score change)
    The core narrative holds: the Sept 7, 2025 exploit of about $2.4-2.6M, the single-developer unaudited deployment, and the Asymptotic warning 27 days earlier are all confirmed by Cointelegraph and CoinDesk. The Wormhole CCTP detail and the MoveBit and January 2025 chronology were not corroborated in the sources I checked, and the NEOM peg and migration claim rests on an unreadable X post. The zero-TVL status matches DeFiLlama data. This was a limited-sample review. I fetched 2 of about 20 cited URLs and did not check the founder, backer and accelerator claims.
    anchoranchored
    chain
    ●mainnet-betaslot 465,085,685
    sig
    5NeetvP8b4NR…ZQWMgjbmexplorer ↗
    hash
    4N49w4HzpW5G…SKuzNREysha256 → base58
    verifying row…full verify ↗
    canonical bytes (1459 B) ▸
    {"actor":"reviewer","artifact_identity":"ed028c84503d8d3addc1388570a4c4f0","blocked_count":1,"decided_at":"2026-11-03T23:36:16.048Z","decision":"review","disputed_pct":0.1429,"findings_hash":"DAvggDLaF148pz3AxFasEjAABHNfjC5ru3bwWBg9vyDJ","investigation_id":"20f595cd-4fa0-459f-930f-f424155f06bd","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":60,"omissions":{"material":0,"total":1},"page_content_hash":"b02331cafa6481c0c26312125115aa8d3da26b23f068229690e028b7bfe9e0e7","page_slug":"nemo-yield-trading","prev_score":60,"reason":"The core narrative holds: the Sept 7, 2025 exploit of about $2.4-2.6M, the single-developer unaudited deployment, and the Asymptotic warning 27 days earlier are all confirmed by Cointelegraph and CoinDesk. The Wormhole CCTP detail and the MoveBit and January 2025 chronology were not corroborated in the sources I checked, and the NEOM peg and migration claim rests on an unreadable X post. The zero-TVL status matches DeFiLlama data. This was a limited-sample review. I fetched 2 of about 20 cited URLs and did not check the founder, backer and accelerator claims.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":7,"sequence_num":3,"subject_status":"operating","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 b15f0667-7f3a-415f-b275-9b96babde2c4
  4. #4review reviseby judgejudge
    2026-11-03 23:36:16Z
    Score: 60 → 60 (no score change)
    The core account of the September 7, 2025 exploit, the single-developer unaudited deployment and the auditor warning 27 days earlier was confirmed by Tier 2 sources (claim_findings[0], [1], [5]). One of seven countable claims (about 14%) could not be verified: the MoveBit submission (claim_findings[2]). The Wormhole CCTP bridge route (claim_findings[3]) was only partly supported and may be wrong, since other outlets describe a route via Arbitrum and Circle. One finding (claim_findings[7]) was excluded because the source blocked the reviewer, and the review sampled only 2 of about 20 cited URLs. No material omissions were found and the page's dormant-protocol status matches the review's status check. The penalty is kept small because reviewer confidence is moderate to low.
    anchoranchored
    chain
    ●mainnet-betaslot 465,085,690
    sig
    4GSPs7XvgPAE…LB5AURLRexplorer ↗
    hash
    6TEvEbDjXo22…ec5AGHsKsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1470 B) ▸
    {"actor":"judge","artifact_identity":"ed028c84503d8d3addc1388570a4c4f0","band_override":null,"blocked_count":1,"decided_at":"2026-11-03T23:36:16.048Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1429,"investigation_id":"20f595cd-4fa0-459f-930f-f424155f06bd","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":60,"page_slug":"nemo-yield-trading","prev_score":60,"reason":"The core account of the September 7, 2025 exploit, the single-developer unaudited deployment and the auditor warning 27 days earlier was confirmed by Tier 2 sources (claim_findings[0], [1], [5]). One of seven countable claims (about 14%) could not be verified: the MoveBit submission (claim_findings[2]). The Wormhole CCTP bridge route (claim_findings[3]) was only partly supported and may be wrong, since other outlets describe a route via Arbitrum and Circle. One finding (claim_findings[7]) was excluded because the source blocked the reviewer, and the review sampled only 2 of about 20 cited URLs. No material omissions were found and the page's dormant-protocol status matches the review's status check. The penalty is kept small because reviewer confidence is moderate to low.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":7,"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 17fee546-2353-4471-9ccf-bfa4a789acc2
  5. #5rescoreby systemsystem
    2026-11-03 23:36:17Z
    Score: 60 → 61 (+1)
    Recalculated after the fact-check of 2026-11-03. Rescored under Scoring v2, the published formula (avoid.net/scoring): 60 → 61. Problems weighed by who is responsible: concerns that are not fraud −6.4, incidents the subject suffered −3.2, problems around the subject, caused by others −0.8; legitimacy credit long-running +6; 1 section(s) set aside until a failed fact-check is resolved.
    anchoranchored
    chain
    ●mainnet-betaslot 465,085,695
    sig
    5cHts1QSv435…oFxfZvLDexplorer ↗
    hash
    CoUgMXWUoTjG…wT3jnwg1sha256 → base58
    verifying row…full verify ↗
    canonical bytes (759 B) ▸
    {"actor":"system","decided_at":"2026-11-03T23:36:16.048Z","decision":"rescore","investigation_id":"20f595cd-4fa0-459f-930f-f424155f06bd","new_score":61,"page_slug":"nemo-yield-trading","prev_score":60,"reason":"Recalculated after the fact-check of 2026-11-03. Rescored under Scoring v2, the published formula (avoid.net/scoring): 60 → 61. Problems weighed by who is responsible: concerns that are not fraud −6.4, incidents the subject suffered −3.2, problems around the subject, caused by others −0.8; legitimacy credit long-running +6; 1 section(s) set aside until a failed fact-check is resolved.","score_delta":1,"score_model":"v2","sequence_num":5,"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 c5bdeb7a-b06b-4aa4-bee5-2162c9bdd1f2
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>.