Fact-check findings

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. #2[disputed][awaiting moderator]in the timeline

   “2025-04-21”

   reviewerTeam compensation plan was published on 2025-04-21The Apr 21 post promised no specific compensation. The detailed plan is bylined Apr 28. Page metadata shows a conflicting 2026 date, but the byline fits the May timelines in the text.
   Proposed correction (not yet applied)

   2025-04-28

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

1. #1[unverifiable][awaiting moderator]in the summary

   “ZachXBT has flagged the entity in the context of trust intelligence monitoring.”

   reviewerZachXBT has flagged numa. in trust intelligence monitoringA search for ZachXBT and Numa returned nothing connecting them, and the page cites no source for this.
2. #7[unverifiable][awaiting moderator]in section: Security Posture and Audit History

   “Both CertiK and Verichains independently analyzed the August exploit and concluded that a thorough security audit including adversarial stress-testing was essential before deploying modified protocol versions to production.”

   reviewerBoth CertiK and Verichains concluded a thorough audit with adversarial stress-testing was essentialThe CertiK extraction contains no such conclusion. The claim remains unconfirmed for CertiK, and I did not check Verichains.
   citedblog.verichains.io/p/numa-incident-analysiswww.certik.com/blog/numa-incident-analysis

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

1. #3[partially supported][awaiting moderator]in section: April 2025 Exploit — Flash Loan Price Manipulation ($506K)

   “The team stated they would not make themselves whole so that external users could be made whole first.”

   reviewerTeam stated it would not make itself whole so that external users are made whole firstThe substance is consistent with the source (debt write-off by team and partners). I did not find the explicit statement the sentence attributes to the team.
   citednuma.money/blog/incident-update-and-moving-forward

The cited evidence supports the claim as written.

1. #4[confirmed][no action needed]in section: April 2025 Exploit — Flash Loan Price Manipulation ($506K)

   “On April 18, 2025 at approximately 9:00 PM UTC, the numa. protocol on Arbitrum suffered a price manipulation exploit resulting in the loss of approximately 292.96 rETH, valued at roughly $506,000–$527,000 at the time of the attack.”

   reviewerApril exploit: approx 292.96 rETH, about $506K, on Apr 18 2025, laundered via Tornado Cash, detected 7+ minutes earlierCore facts, timing and the one-hour discovery are supported. I did not verify the contract address or tx hash because Hypernative does not list them.
   citedwww.hypernative.io/blog/hypernative-dete…oney-on-arbitrumnuma.money/blog/update-on-recent-securit…t-affecting-numa
2. #5[confirmed][no action needed]in section: August 2025 Exploit — Collateral Valuation Logic Flaw ($313K)

   “On August 10, 2025, numa. suffered a second exploit, this time on the Sonic blockchain, resulting in a loss of approximately $313,000 (74.3 ETH).”

   reviewerAugust 10 2025 Sonic exploit, ~$313K (74.3 ETH), attacker and contract addresses, 74.2 ETH to Tornado CashMatches the CertiK analysis.
   citedwww.certik.com/blog/numa-incident-analysis
3. #6[confirmed][no action needed]in the timeline

   “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.”

   reviewerRemediation: Sherlock review required before deploy; short ability removed; Sonic launch end of MaySupported. The post is bylined April 28, so the 2025-05 date is slightly late but the announcement is real.
   citednuma.money/blog/incident-update-and-moving-forward