Skip to main content
Sign in
numa.1 decision on this page

Audit log

Every state-changing event for numa.: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions carry three independent witnesses — the original source, an Internet Archive snapshot taken at submission time, and a Solana memo signed by our publicly-disclosed publisher key.

  1. #1publishby system:backfill
    2026-05-29 17:23:49Z
    Score: ?? (no score change)
    anchoranchored
    chain
    mainnet-betaslot 422,983,115
    sig
    4yn582nxNWAy…dtn7iVsTexplorer ↗
    hash
    DeNS5fHnn138…DQmv4WvCsha256 → base58
    verifying row…full verify ↗
    canonical bytes (5690 B) ▸
    {"actor":"system:backfill","investigation_id":"4e0807c8-b31e-45cb-8db3-3c303761446e","kind":"publish","page_slug":"numa","published_at":"2026-05-29T17:23:49.367Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"numa.","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://numa.money/","type":"other","url":""},{"credibility":3,"name":"https://numa-1.gitbook.io/numa-v3-white-paper/introduction/summary","type":"other","url":""},{"credibility":3,"name":"https://www.chainlinkecosystem.com/ecosystem/numamoney","type":"other","url":""},{"credibility":3,"name":"https://coinpaprika.com/coin/numa-numa/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://numa.money/blog/update-on-recent-security-incident-affecting-numa","type":"other","url":""},{"credibility":3,"name":"https://numa.money/blog/incident-update-and-moving-forward","type":"other","url":""},{"credibility":3,"name":"https://www.hypernative.io/blog/hypernative-detection-506k-exploit-of-numa-money-on-arbitrum","type":"other","url":""},{"credibility":3,"name":"https://olympixai.medium.com/dexodus-zora-numa-946k-lost-to-replays-access-bugs-and-locked-in-prices-40c37b78391c","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://blog.verichains.io/p/numa-incident-analysis","type":"other","url":""},{"credibility":3,"name":"https://www.certik.com/blog/numa-incident-analysis","type":"other","url":""},{"credibility":3,"name":"https://nominis.io/insights/nominis-monthly-report-crypto-attacks-in-september-2025","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.coingecko.com/en/coins/numa","type":"other","url":""},{"credibility":3,"name":"https://www.coinbase.com/price/numa","type":"other","url":""},{"credibility":3,"name":"https://www.hypernative.io/blog/hypernative-detection-506k-exploit-of-numa-money-on-arbitrum","type":"other","url":""},{"credibility":3,"name":"https://beincrypto.com/price/numa/price-prediction/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://numa.money/blog/incident-update-and-moving-forward","type":"other","url":""},{"credibility":3,"name":"https://blog.verichains.io/p/numa-incident-analysis","type":"other","url":""},{"credibility":3,"name":"https://www.certik.com/blog/numa-incident-analysis","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.hypernative.io/blog/hypernative-detection-506k-exploit-of-numa-money-on-arbitrum","type":"other","url":""},{"credibility":3,"name":"https://blog.verichains.io/p/numa-incident-analysis","type":"other","url":""},{"credibility":3,"name":"https://www.certik.com/blog/numa-incident-analysis","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://numa.money/blog/update-on-recent-security-incident-affecting-numa","type":"other","url":""},{"credibility":3,"name":"https://numa.money/blog/incident-update-and-moving-forward","type":"other","url":""},{"credibility":3,"name":"https://numa.money/","type":"other","url":""}]}],"sources_used":[],"summary":"numa. (stylized with a period) is a non-custodial DeFi protocol on Arbitrum and Sonic that issues LST-backed synthetic assets (nuUSD, nuBTC, nuETH, nuGOLD) through a burn-and-mint tokenomics model. The protocol suffered two separate exploits in 2025 — a $506K price manipulation attack in April and a $313K collateral valuation exploit in August — resulting in cumulative losses exceeding $800K and a token price decline of approximately 99% from its peak. ZachXBT has flagged the entity in the context of trust intelligence monitoring.","timeline":[{"date":"2024-12-01","event":"numa. protocol launches on Arbitrum with LST-backed synthetics (nuUSD, nuBTC, nuETH, nuGOLD) and burn-and-mint tokenomics.","source":""},{"date":"2025-04-18","event":"First exploit: attacker uses flash loan to manipulate $NUMA internal price via sell-burn-lock mechanism, stealing approximately 292.96 rETH (~$506K). Hypernative detected the attack 7+ minutes prior to execution. Stolen funds bridged to Ethereum and laundered through Tornado Cash.","source":""},{"date":"2025-04-18","event":"Numa team discovers exploit approximately one hour after execution. Protocol pauses lending and liquidation functionality.","source":""},{"date":"2025-04-21","event":"$NUMA token hits all-time low of approximately $0.13, down roughly 60% from pre-exploit price.","source":""},{"date":"2025-04-21","event":"Team publishes compensation plan: ~35 rETH in vault rewards, $100K external contribution, and direct team/protocol funds to make 1.49M $NUMA owed to external users whole.","source":""},{"date":"2025-05-01","event":"Team announces Sonic blockchain launch planned for end of May 2025, with Sherlock audit review required before deployment. Arbitrum lending to reopen after Sonic launch.","source":""},{"date":"2025-08-10","event":"Second exploit: attacker flash-mints nuBTC to inflate synthValueInEth, collapsing cNuma collateral prices and triggering forced liquidations of five victim accounts on Sonic. Approximately $313K (74.3 ETH) stolen. Funds bridged to Ethereum and deposited into Tornado Cash.","source":""},{"date":"2025-08-01","event":"Olympix publishes analysis of the August exploit, categorizing it as a locked-in price manipulation vulnerability. CertiK and Verichains publish independent post-mortems.","source":""}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision b4c2090c-048b-444f-82d4-db0f85eecefe
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>.