Skip to main content
AVOID.NET
← Sagareviewed 2026-10-28 · 11 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Saga 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

3 claims

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

  1. #9[unverifiable][awaiting moderator]in section: Protocol overview and team
    “The mainnet and SAGA token launched on April 9, 2024, with 1 billion SAGA created at genesis, following a record $13.4 billion staked on Binance.”
    reviewerBinance Launchpool record of $13.4B staked, launch April 9, 2024.Not independently fetched in this review; plausible and consistent with multiple cited sources, but not verified.
  2. #10[unverifiable][awaiting moderator]in section: Market impact
    “No formal compensation or recovery plan for affected users, and no regulatory action or law enforcement referral, has been publicly disclosed.”
    reviewerNo formal compensation plan, regulatory action or law enforcement referral disclosed.Searches found nothing either way; a negative claim.
  3. #11[unverifiable][awaiting moderator]in the timeline
    “Saga raises a $5 million seed extension round led by Placeholder, bringing total funding to over $13.5 million.”
    reviewerPlaceholder-led $5M seed extension, $6.5M seed at $130M valuation, over $13.5M total.Not fetched. $6.5M + $5M is $11.5M, so 'over $13.5 million total' implies other funding not shown on the page; also the 2023 date is unsourced (empty source field).

stale

1 claim

The claim was accurate when written but events since have overtaken it.

  1. #8[stale][awaiting moderator]in section: Team response and remediation
    “an all-time low of about $0.053 around October 2025, roughly 99% below the peak”
    reviewerSAGA all-time low of about $0.053 around October 2025.Stale and internally inconsistent: the page also says SAGA fell to about $0.053 in Jan 2026 and had a $19.5M cap in May 2026. A precise replacement low and date was not verified, so no edit is proposed.

partially supported

4 claims

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

  1. #3[partially supported][awaiting moderator]in section: January 2026 SagaEVM exploit
    “Saga paused SagaEVM at block height 6,593,800; the chain remained offline pending a full post-mortem.”
    reviewerSaga halted at block 6,593,800 and mainnet/validators were unaffected.Pause facts are right, but the 'pending a full post-mortem' framing is superseded by the announced SagaEVM sunset.
  2. #4[partially supported][awaiting moderator]in section: Technical root cause: inherited Ethermint vulnerability
    “The vulnerability was not authored by Saga but was inherited from upstream code, and Saga deployed the affected module without identifying or patching it before mainnet operation.”
    reviewerSaga deployed the affected module without identifying or patching it before mainnet operation.Inheritance is supported. The implication of fault for not patching is not, since the flaw was not publicly known before the exploit.
  3. #5[partially supported][awaiting moderator]in section: Technical root cause: inherited Ethermint vulnerability
    “Cosmos Labs coordinated with 15 identified affected chains to distribute the patched v0.6.0 before public disclosure in March 2026;”
    reviewerPer Halborn, forked implementation; advisory affects all versions before v0.6.0, Critical, 15 affected chains, disclosure March 2026.Substantially accurate; the advisory says the others applied mitigation, with one chain (Saga) exploited first.
  4. #7[partially supported][awaiting moderator]in section: Fund flows and laundering
    “Another account states generally that about $7 million of user funds were permanently moved to Tornado Cash before recovery efforts could succeed.”
    reviewerTimeline: Jan 24 LP NFT transfer is dated only 2026-01 (fine) but summary says 'most of it reportedly laundered'; and Halborn did not give figures.The $7M-to-Tornado figure conflicts with the CertiK $6.2M figure on the same page and is not found in Halborn.

confirmed

3 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in the summary
    “On January 21, 2026, its SagaEVM chainlet lost about $7 million when an attacker exploited an inherited Ethermint ICS20 precompile vulnerability to mint unbacked Saga Dollar stablecoin, most of it reportedly laundered via Tornado Cash.”
    reviewerOn January 21, 2026 SagaEVM lost about $7 million to an exploit.Date, amount, root cause and Tornado Cash routing all supported.
  2. #2[confirmed][no action needed]in section: January 2026 SagaEVM exploit
    “The attacker deployed a helper contract (0x7D69E4376535cf8c1E367418919209f70358581E) that crafted fake IBC messages mimicking legitimate collateral deposits, which the precompile accepted as authentic, triggering unauthorized minting through the Colt protocol, and the attacker's primary wallet was identified as 0x2044697623afa31459642708c83f04ecef8c6ecb.”
    reviewerHelper contract and attacker wallet addresses, ETH proceeds and LP positions.Addresses match Rekt exactly.
  3. #6[confirmed][no action needed]in section: Fund flows and laundering
    “According to CertiK, $6.2 million of the stolen funds were deposited into Tornado Cash using five separate wallets; about $847,000 in LP positions remained traceable at the time of reporting.”
    reviewerCertiK: $6.2M to Tornado Cash across five wallets; ~$847K LP traceable; LP NFTs moved Jan 24 to secondary wallet.Supported.
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.