Skip to main content
AVOID.NET
Unibot4 decisions on this page

Audit log

Every state-changing event for Unibot: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.

  1. #1publishby system:backfill
    2026-05-30 11:48:06Z
    Score: ?? (no score change)
    anchoranchored
    chain
    mainnet-betaslot 423,150,316
    sig
    4fuNFvLSVqhN…c6sWqUXgexplorer ↗
    hash
    KxBUCRpZpaid…et8Cp43Msha256 → base58
    verifying row…full verify ↗
    canonical bytes (7805 B) ▸
    {"actor":"system:backfill","investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","kind":"publish","page_slug":"unibot","published_at":"2026-05-30T11:48:06.786Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Unibot","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.iconomi.com/blog/what-is-unibot","type":"other","url":""},{"credibility":3,"name":"https://crypto.com/us/university/what-is-unibot","type":"other","url":""},{"credibility":3,"name":"https://learn.unibot.app/faq/revenue-sharing","type":"other","url":""},{"credibility":3,"name":"https://beincrypto.com/learn/unibot-guide/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.coindesk.com/markets/2023/10/31/unibot-token-hurtles-25-as-telegram-bot-exploited-for-630k","type":"other","url":""},{"credibility":3,"name":"https://cointelegraph.com/news/unibot-contract-560-k-exploit-crashes-token-price-40","type":"other","url":""},{"credibility":3,"name":"https://thecryptobasic.com/2023/10/31/unibot-suffers-560k-exploit-users-endure-more-pain-as-token-dumps-33/","type":"other","url":""},{"credibility":3,"name":"https://revoke.cash/exploits/unibot","type":"other","url":""},{"credibility":3,"name":"https://www.certik.com/resources/blog/1Zh5XbaDstXKteFcRSmOcp-maestro-and-unibot","type":"other","url":""},{"credibility":3,"name":"https://rivanorth.com/blog/unibot-hack","type":"other","url":""},{"credibility":3,"name":"https://finance.yahoo.com/news/unibot-token-price-crashes-30-073233496.html","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.cryptotimes.io/2023/11/04/unibot-reimburses-users-following-recent-security-hack/","type":"other","url":""},{"credibility":3,"name":"https://chainbulletin.com/unibot-to-compensate-users-affected-by-exploit","type":"other","url":""},{"credibility":3,"name":"https://cryptopotato.com/unibot-fully-compensates-users-following-hacking-incident/","type":"other","url":""},{"credibility":3,"name":"https://www.coindesk.com/markets/2023/10/31/unibot-token-hurtles-25-as-telegram-bot-exploited-for-630k","type":"other","url":""},{"credibility":3,"name":"https://revoke.cash/exploits/unibot","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.dlnews.com/articles/defi/unibot-telegram-bot-unveils-cloud-service-for-private-keys/","type":"other","url":""},{"credibility":3,"name":"https://cointelegraph.com/news/should-telegram-trading-bots-be-trusted","type":"other","url":""},{"credibility":3,"name":"https://www.certik.com/resources/blog/1Zh5XbaDstXKteFcRSmOcp-maestro-and-unibot","type":"other","url":""},{"credibility":3,"name":"https://www.iconomi.com/blog/what-is-unibot","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.dlnews.com/articles/defi/unibot-devs-tussle-as-ethereum-team-splits-from-solana-group/","type":"other","url":""},{"credibility":3,"name":"https://www.coindesk.com/markets/2024/03/11/unibot-tanks-33-after-ending-collaboration-with-solana-group","type":"other","url":""},{"credibility":3,"name":"https://crypto.news/unibot-collapse-solana-termination/","type":"other","url":""},{"credibility":3,"name":"https://www.odaily.news/en/post/5188638","type":"other","url":""},{"credibility":3,"name":"https://fullycrypto.com/unibot-dumps-solana-over-unauthorized-bot-launch","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.coingecko.com/en/coins/unibot","type":"other","url":""},{"credibility":3,"name":"https://coinmarketcap.com/currencies/unibot-eth/","type":"other","url":""},{"credibility":3,"name":"https://coinpedia.org/guest-post/unibot-dives-as-bitbot-gears-up-to-become-next-big-crypto-of-2024/","type":"other","url":""},{"credibility":3,"name":"https://medium.com/@DeMan01/unibot-alternative-can-banana-gun-sustain-its-recent-impressive-data-performance-in-the-near-term-211dadc3112b","type":"other","url":""},{"credibility":3,"name":"https://www.linkedin.com/pulse/banana-guns-users-surpass-both-unibot-maestro-theblockcrypto","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.odaily.news/en/post/5188638","type":"other","url":""},{"credibility":3,"name":"https://www.dlnews.com/articles/defi/unibot-devs-tussle-as-ethereum-team-splits-from-solana-group/","type":"other","url":""},{"credibility":3,"name":"https://learn.unibot.app/faq/revenue-sharing","type":"other","url":""},{"credibility":3,"name":"https://medium.com/coinmonks/things-to-consider-before-venturing-into-unibot-3d878819d547","type":"other","url":""}]}],"sources_used":[],"summary":"Unibot is a Telegram-based trading bot launched in May 2023 that enabled users to execute Uniswap trades directly within Telegram. On October 31, 2023, a newly deployed router contract containing a call injection vulnerability was exploited, draining approximately $560,000–$640,000 in user funds that were subsequently laundered through Tornado Cash; the team ultimately reimbursed affected users at a reported cost of $1.78 million. A second crisis followed in March 2024 when the Ethereum and Solana development teams publicly split amid mutual accusations of unauthorized deployments and revenue misappropriation, causing the token to shed an additional 40% of its value and reducing the project to a fraction of its former user base.","timeline":[{"date":"2023-05-17","event":"Unibot launches on Ethereum mainnet with 1,000,000 UNIBOT tokens in a claimed fair launch with no presale or team allocation.","source":""},{"date":"2023-08-16","event":"UNIBOT token reaches its all-time high of approximately $236–$238, with the project reporting a growing user base and significant trading volume.","source":""},{"date":"2023-10-28","event":"Unibot deploys a new router contract on Ethereum. The contract is not verified on Etherscan at the time of deployment.","source":""},{"date":"2023-10-31","event":"A call injection vulnerability in the new router contract is exploited. Approximately $560,000–$640,000 in user funds is drained. Scopescan publicly discloses the ongoing attack. The team pauses the router. UNIBOT token falls 25–42% within hours. Stolen ETH (approximately 355.5 ETH) is subsequently laundered through Tornado Cash.","source":""},{"date":"2023-11-02","event":"Unibot resumes trading operations after pausing the compromised router contract.","source":""},{"date":"2023-11-04","event":"Unibot reports full reimbursement of approximately 600 affected users, disclosing the compensation effort cost approximately $1.78 million. Zero trading fees and increased revenue share announced as additional remediation.","source":""},{"date":"2024-03-11","event":"Unibot's Ethereum and Solana development teams publicly announce the end of their collaboration. Ethereum team accuses Solana team of unauthorized Blast deployment, KYC refusal, and fee violations. Solana team (Reethmos) counter-accuses Ethereum developers of tax farming extraction and engineering the split. UNIBOT token falls over 40%, losing approximately $40 million in market cap.","source":""},{"date":"2024-03-11","event":"Ethereum team launches 'Unisol X' as an alternative Solana frontend; Solana team continues operating under the original 'Unibot on Solana' branding.","source":""},{"date":"2025-01-01","event":"UNIBOT token trading at approximately $1–$4, down approximately 98–99% from its August 2023 all-time high. Daily active users reported at approximately 600, down from a peak of 32,000.","source":""}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision c3cfd390-3ced-45d2-8d39-3b500c55a3d3
  2. #2reviewby reviewerreviewer
    2026-08-18 21:01:32Z
    Score: 4242 (no score change)
    The page's core narrative -- a May 2023 Telegram trading bot that suffered a ~$560-640K router-contract exploit on Oct 31, 2023 (fully reimbursed at $1.78M cost to the team), followed by a March 2024 acrimonious split between its Ethereum and Solana dev factions -- is well-corroborated by multiple independent, credible sources and no link rot was found in spot checks. The one material defect found is the timeline's '32,000 peak daily active users' figure, which is contradicted by every source located (independent reporting places Unibot's DAU all-time high at 3,151-4,730, an order of magnitude lower); this inflates the apparent scale of the project's subsequent collapse and should be corrected or sourced. No unhedged criminal allegations were found: the exploit is consistently and correctly framed as something Unibot suffered (a victim of an external attacker), not something Unibot's team perpetrated, and the March 2024 dev-team dispute is presented as competing, unadjudicated accusations between two factions rather than as established fact.
    anchoranchored
    chain
    mainnet-betaslot 443,508,868
    sig
    34vddGEBGUXT…pYYGuSuGexplorer ↗
    hash
    Gubtz88BSug6…JgWSiHPGsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1399 B) ▸
    {"actor":"reviewer","decided_at":"2026-08-18T21:01:31.896Z","decision":"review","investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","new_score":42,"page_slug":"unibot","prev_score":42,"reason":"The page's core narrative -- a May 2023 Telegram trading bot that suffered a ~$560-640K router-contract exploit on Oct 31, 2023 (fully reimbursed at $1.78M cost to the team), followed by a March 2024 acrimonious split between its Ethereum and Solana dev factions -- is well-corroborated by multiple independent, credible sources and no link rot was found in spot checks. The one material defect found is the timeline's '32,000 peak daily active users' figure, which is contradicted by every source located (independent reporting places Unibot's DAU all-time high at 3,151-4,730, an order of magnitude lower); this inflates the apparent scale of the project's subsequent collapse and should be corrected or sourced. No unhedged criminal allegations were found: the exploit is consistently and correctly framed as something Unibot suffered (a victim of an external attacker), not something Unibot's team perpetrated, and the March 2024 dev-team dispute is presented as competing, unadjudicated accusations between two factions rather than as established fact.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision e3db1122-fef0-401a-9b5f-ca473fde47f1
  3. #3review reviseby judgejudge
    2026-08-18 21:01:32Z
    Score: 4258 (+16)
    Content accuracy holds up well -- 7 of 10 claims confirmed outright, disputed_pct is only 0.1, and no unhedged criminal allegations were found (claim_findings[7] correctly frames the March 2024 dev split as a mutual, unresolved dispute rather than adjudicated fraud). The score is the problem: the page's own rubric (calibration.scoring_instruction) states that 'suffered' incidents cap an entity at CAUTIONARY (50-69), yet the current score of 42 sits in WARNING, which per that same rubric implies own-conduct fraud or negligence. Both major incidents -- the October 2023 router exploit (calibration_assessment.incident_attributions[0], attribution 'b': external attacker, fully reimbursed at $1.78M) and the March 2024 dev-team split (incident_attributions[1], attribution 'c': mutual unresolved accusations between two pseudonymous factions) -- are suffered/third-party events, not own-fraud. The current WARNING score conflates being hacked and having an internal governance dispute with entity misconduct, which the evidence does not support; 58 (upper-CAUTIONARY) better reflects a project that responded responsibly to victimization but still carries real, unresolved governance and staleness risk. Notes: (Correct or source the timeline[8] '32,000 peak daily active users' figure -- no source located supports it, and independent reporting places Unibot's DAU all-time high at 3,151-4,730, roughly an order of magnitude lower (claim_findings[9]).) (Adjust timeline[7] to reflect that Unisol X launched March 14, 2024, three days after the March 11 split announcement, rather than compressing both into the same date (claim_findings[8]).)
    anchoranchored
    chain
    mainnet-betaslot 443,508,870
    sig
    5yyC1j6k5nbq…V3hpvaWYexplorer ↗
    hash
    BheeKn5cGhTS…nNj4iqsesha256 → base58
    verifying row…full verify ↗
    canonical bytes (1993 B) ▸
    {"actor":"judge","decided_at":"2026-08-18T21:01:31.896Z","decision":"review_revise","investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","new_score":58,"page_slug":"unibot","prev_score":42,"reason":"Content accuracy holds up well -- 7 of 10 claims confirmed outright, disputed_pct is only 0.1, and no unhedged criminal allegations were found (claim_findings[7] correctly frames the March 2024 dev split as a mutual, unresolved dispute rather than adjudicated fraud). The score is the problem: the page's own rubric (calibration.scoring_instruction) states that 'suffered' incidents cap an entity at CAUTIONARY (50-69), yet the current score of 42 sits in WARNING, which per that same rubric implies own-conduct fraud or negligence. Both major incidents -- the October 2023 router exploit (calibration_assessment.incident_attributions[0], attribution 'b': external attacker, fully reimbursed at $1.78M) and the March 2024 dev-team split (incident_attributions[1], attribution 'c': mutual unresolved accusations between two pseudonymous factions) -- are suffered/third-party events, not own-fraud. The current WARNING score conflates being hacked and having an internal governance dispute with entity misconduct, which the evidence does not support; 58 (upper-CAUTIONARY) better reflects a project that responded responsibly to victimization but still carries real, unresolved governance and staleness risk. Notes: (Correct or source the timeline[8] '32,000 peak daily active users' figure -- no source located supports it, and independent reporting places Unibot's DAU all-time high at 3,151-4,730, roughly an order of magnitude lower (claim_findings[9]).) (Adjust timeline[7] to reflect that Unisol X launched March 14, 2024, three days after the March 11 split announcement, rather than compressing both into the same date (claim_findings[8]).)","score_delta":16,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision ee507895-1aeb-4161-a675-1d525e13d647
  4. #4reviewby reviewerreviewer
    2026-09-09 03:05:33Z
    Score: 4848 (no score change)
    Findings-only fact-check (retroactive anchor of stored findings)
    anchoranchored
    chain
    mainnet-betaslot 445,508,509
    sig
    S13vJXZEmCcw…bUsGQ68rexplorer ↗
    hash
    8T7WVS4qMz39…NbPXyaXosha256 → base58
    verifying row…full verify ↗
    canonical bytes (699 B) ▸
    {"actor":"reviewer","artifact_identity":"ed67db9e7a989422343e72f22bf8abc1","decided_at":"2026-09-07T05:45:37.582831+00:00","decision":"review","findings_count":22,"findings_rows_hash":"771f87f5caf54df57eea52b6a8bedb1860b976b56cb7a8848ef749f6a19de8d9","investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","mode":"findings_only_retroactive","new_score":48,"page_content_hash":"83bc428633f2353b4c284380996aa5e721c37ffff393977e8a9be7d5e34f8699","page_slug":"unibot","prev_score":48,"reason":"Findings-only fact-check (retroactive anchor of stored findings)","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 0dcdb162-da94-4e70-87c8-fa4228b1e8df
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>.