Skip to main content
AVOID.NET
← Shidoreviewed 2026-11-02 · 12 claims checked

Fact-check findings

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

disputed 2unverifiable 4stale 2confirmed 44 corrections pending · 0 applied

disputed

2 claims

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. #3[disputed][awaiting moderator]in section: Technical Root Cause: Access Control Failure
    “Once the attacker controlled the owner key, the upgrade to add a hidden withdrawToken() function and the subsequent drain of the contract were executed in a single atomic sequence. The exploit was recorded on-chain via the transaction hash 0xaa76ea503fadddf775b1ef7f195676440fdc3ac46ab642798ab6fa7ae3aafcbe.”
    reviewerExploit was recorded in a single transaction hash and the upgrade and drain were a single atomic sequenceThe cited hash is the ownership transfer, not the whole exploit, and the source does not say the steps were atomic.
    Proposed correction (not yet applied)
    Once the attacker controlled the owner key, the upgrade to add a hidden withdrawToken() function and the subsequent drain of the contract followed in rapid succession. The ownership transfer was recorded on-chain via the transaction hash 0xaa76ea503fadddf775b1ef7f195676440fdc3ac46ab642798ab6fa7ae3aafcbe.
  2. #5[disputed][awaiting moderator]in the timeline
    “ZachXBT traces exploiter funding through Across protocol (Arbitrum) and Layerswap; identifies alleged link to OKX and Concentric Finance hacks via shared attacker infrastructure.”
    reviewerZachXBT identified alleged link between Shido and the OKX/Concentric hacks via shared attacker infrastructureFunding-route part confirmed; the OKX/Concentric link is unsupported by any reachable source.
    Proposed correction (not yet applied)
    ZachXBT traces exploiter funding through Across protocol (Arbitrum) and Layerswap.

unverifiable

4 claims

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

  1. #4[unverifiable][awaiting moderator]in the summary
    “On-chain investigator ZachXBT linked the exploit to a serial hacker responsible for the OKX (December 2023) and Concentric Finance (January 2024) hacks, with the attack vector in each case being private key compromise via social engineering.”
    reviewerZachXBT linked the Shido exploit to the OKX and Concentric Finance hacks, as a serial hackerOKX-Concentric link is documented; a Shido link and 'private key compromise via social engineering' as the Shido vector are not found in any fetched source. The only readable source that could support it (Medium) was blocked, but other searches found nothing.
  2. #9[unverifiable][awaiting moderator]in section: Post-Exploit Status and Token Price
    “The project has reportedly pursued additional exchange listings and commissioned third-party smart contract audits following the incident.”
    reviewerProject reportedly pursued additional exchange listings and commissioned third-party audits after the incidentNo fetched source supports post-incident listings or audits; hedged with 'reportedly' but uncited.
  3. #10[unverifiable][awaiting moderator]in section: Team Response and Alleged Refund Commitments
    “The team also replaced the compromised deployer address, temporarily suspended liquidity provisioning on all decentralized exchanges, and contacted centralized exchanges to disable deposits and freeze tokens associated with the hack.”
    reviewerTeam response: stakers refunded, deployer replaced, DEX liquidity suspended, CEX freezes, bounty invitationCited source blocked. Search snippets corroborate the refund promise and bounty invitation only.
  4. #12[unverifiable][awaiting moderator]in section: Project Background and Leadership
    “Shido Network was founded in 2021 and is based in Bromma, Sweden. The project's stated co-founders are Bjorn Bonnevier (CEO) and Edin Maloku.”
    reviewerFounded 2021 in Bromma, Sweden by Bjorn Bonnevier and Edin MalokuNot checked against tracxn or shido.io in this pass; crypto.news does not mention founders.

stale

2 claims

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

  1. #7[stale][awaiting moderator]in section: Team Response and Alleged Refund Commitments
    “The project's token remains approximately 98.8% below its all-time high as of mid-2026.”
    reviewerSHIDO price is ~98.8% below ATH as of mid-2026Current CoinGecko shows 99.5%.
    Proposed correction (not yet applied)
    The project's token remains approximately 99.5% below its all-time high as of November 2026.
  2. #8[stale][awaiting moderator]in section: Post-Exploit Status and Token Price
    “CoinGecko data shows the token reached an all-time high of approximately $0.01277 and had fallen roughly 98.8% from that peak. The 24-hour trading volume as of the most recent data is approximately $60,461.”
    reviewerToken fell ~98.8% from ATH $0.01277; 24h volume ~$60,461ATH matches; percentage and volume are out of date (volatile figures).
    Proposed correction (not yet applied)
    CoinGecko data shows the token reached an all-time high of approximately $0.01277 and had fallen roughly 99.5% from that peak. The 24-hour trading volume as of the most recent data is approximately $12,936.

confirmed

4 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: The February 2024 Staking Contract Exploit
    “This function was immediately called to withdraw all 4,353,473,223.864904 SHIDO tokens — approximately half of the roughly 9 billion token circulating supply.”
    reviewerAttacker drained 4,353,473,223.864904 SHIDO, about half of ~9 billion circulating supply, nominally ~$35MFigures match PeckShield numbers reported by both sources.
  2. #2[confirmed][no action needed]in section: The February 2024 Staking Contract Exploit
    “the attacker ultimately converted the position to approximately 956 ETH, representing roughly $3.3 million in realized proceeds”
    reviewerAttacker realized ~956 ETH, ~$3.3MSupported via secondary citation of Web3 Is Going Great; primary page not fetched.
  3. #6[confirmed][no action needed]in section: ZachXBT Investigation and Serial Hacker Link
    “ZachXBT noted that the funding wallet used to initiate the Shido attack appeared to have itself been compromised, as its assets were unexpectedly transferred shortly before funding the exploiter”
    reviewerZachXBT noted funding wallet appeared compromisedSupported.
  4. #11[confirmed][no action needed]in the timeline
    “Shido announces mainnet launch scheduled for the following week.”
    reviewerMainnet launch announced Feb 24, 2024 for following weekSupported.
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.