Skip to main content
AVOID.NET
← SKYDAO Premature Sync Exploit (September 2026)reviewed 2026-10-27 · 8 claims checked

Fact-check findings

What an automated fact-checker found when it re-read SKYDAO Premature Sync Exploit (September 2026) 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 3partially supported 1confirmed 40 corrections pending · 0 applied

unverifiable

3 claims

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

  1. #4[unverifiable][awaiting moderator]in section: Alleged Attack Sequence and Financial Loss
    “The PoC identifies a specific on-chain transaction hash, attacker address, SKYDAO token contract, pool-controller contract, and SKYDAO/USDT pair address as supporting evidence.”
    reviewerThe PoC identifies a specific tx hash, attacker address, token contract, controller and pair addressCould not confirm from the fetched PR text. The PoC source file may contain these, but the page gives none of them.
  2. #5[unverifiable][awaiting moderator]in section: Alleged Attack Sequence and Financial Loss
    “A dexscreener listing for a BSC pair at the same address cited in the PoC (0x096e08dda1e18625ffdfbae4bb65a414aa7ec2c8) independently corroborates the existence of an active SKYDAO/USDT PancakeSwap pair, though it does not itself confirm the exploit.”
    reviewerDexscreener lists an active SKYDAO/USDT PancakeSwap pair at the cited addressBlocked by 403. The word 'active' is questionable for a pair whose USDT reserve was reportedly drained.
  3. #8[unverifiable][awaiting moderator]in section: Absence of Project Response or Patch Confirmation
    “The lack of any identifiable team communication or security audit history is itself a risk indicator, independent of the specific exploit allegations, and should be weighed accordingly.”
    reviewerSKYDAO was a low-liquidity BSC token, and the lack of audit history is itself a risk indicatorThis is an editorial inference, not a sourced fact. 'Low-liquidity' and the absence of an audit are not supported by a cited source.

partially supported

1 claim

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

  1. #6[partially supported][awaiting moderator]in section: Limited Independent Verification
    “documents a structurally similar "burn-from-pair and sync()" attack that same month against a different BSC token (RWC), which lost approximately $109,461”
    reviewerNominis report documents a similar burn-from-pair and sync attack on RWC in September 2026 with a loss of about $109,461, and does not name SKYDAOThe substance is right and the page correctly says SKYDAO is not named. The quoted phrase is presented as the report's wording, which it is not.

confirmed

4 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in the summary
    “On September 30, 2026, an attacker allegedly used a flash loan to exploit this flaw, draining the pair's entire USDT reserve and netting roughly $60,000 in profit from an approximately $183,000 reserve loss.”
    reviewerAttack occurred 2026-09-30 and the attacker netted roughly $60,000 from a ~$183,000 reserve lossMatches the PR. Single-source, and the page hedges accordingly.
  2. #2[confirmed][no action needed]in section: Alleged Attack Sequence and Financial Loss
    “The attacker allegedly flash-borrowed 2,656,932.60 USDT, used part of it (435,367.43 USDT, inclusive of an alleged 35% buy tax) to purchase SKYDAO tokens”
    reviewerFlash loan size, buy size with 35% buy tax, and net profit figuresFigures match.
  3. #3[confirmed][no action needed]in section: Alleged Attack Vector: Burn-From-Pair and Premature Sync
    “The proof-of-concept states the sell path had no owner or admin access controls, making it exploitable by any user who could structure the correct sequence of calls.”
    reviewerSell path has 35% tax, gross amount to pool controller, pair credited with net 65%; no owner/admin gateSupported. The page could note that the controller source is unverified.
  4. #7[confirmed][no action needed]in section: Absence of Project Response or Patch Confirmation
    “No official post-mortem, incident disclosure, or confirmed contract patch attributable to a SKYDAO team could be identified through web search as of this investigation.”
    reviewerNo independent coverage, official post-mortem, or patch locatedConsistent with my searches. The cited PR cannot itself prove a negative, so this is a weak citation.
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.