← Qubit Finance3 decisions on this page
Audit log
Every state-changing event for Qubit Finance: 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.
- #1publishby system:backfill2026-05-20 22:36:30ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 421,077,048
- sig
4ZUJiZMXMzYY…bNoeb2dZexplorer ↗- hash
EhzA6kJzwANP…mqBiUenjsha256 → base58
verifying row…full verify ↗canonical bytes (6545 B) ▸
{"actor":"system:backfill","investigation_id":"d90e7a11-4928-45d2-87e7-45da166374d3","kind":"publish","page_slug":"qubit","published_at":"2026-05-20T22:36:30.745Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Qubit Finance","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://pancakebunny.medium.com/introducing-qubit-qbt-innovating-lending-and-borrowing-on-the-bsc-9f3fe6438f44"},{"credibility":3,"name":"","type":"other","url":"https://pancakebunny.medium.com/pancake-bunny-x-binance-labs-introducing-your-team-mound-288c21209375"},{"credibility":3,"name":"","type":"other","url":"https://qbt.wiki/en/company/mound-inc/"},{"credibility":3,"name":"","type":"other","url":"https://chainbulletin.com/pancakebunny-suffers-from-flash-loan-attack"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://medium.com/@QubitFin/protocol-exploit-report-305c34540fa3"},{"credibility":3,"name":"","type":"other","url":"https://certik.medium.com/qubit-bridge-collapse-exploited-to-the-tune-of-80-million-a7ab9068e1a0"},{"credibility":3,"name":"","type":"other","url":"https://slowmist.medium.com/our-analysis-of-the-80m-qubit-finance-exploit-b0f272cd8c25"},{"credibility":3,"name":"","type":"other","url":"https://www.halborn.com/blog/post/explained-the-qubit-hack-january-2022"},{"credibility":3,"name":"","type":"other","url":"https://rekt.news/qubit-rekt"},{"credibility":3,"name":"","type":"other","url":"https://medium.com/@QubitFin/protocol-exploit-report-2-30aade4d66de"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://rekt.news/qubit-rekt"},{"credibility":3,"name":"","type":"other","url":"https://certik.medium.com/qubit-bridge-collapse-exploited-to-the-tune-of-80-million-a7ab9068e1a0"},{"credibility":3,"name":"","type":"other","url":"https://bscscan.com/address/0x17b7163cf1dbd286e262ddc68b553d899b93f526"},{"credibility":3,"name":"","type":"other","url":"https://blog.merklescience.com/hacktrack/analysis-of-qubit-finance-exploit"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://medium.com/@QubitFin/our-compensation-plan-1-63e7c64738ed"},{"credibility":3,"name":"","type":"other","url":"https://www.bitdefender.com/en-us/blog/hotforsecurity/qubit-pleads-with-hacker-to-return-80-million-of-stolen-funds"},{"credibility":3,"name":"","type":"other","url":"https://finance.yahoo.com/news/losing-80-million-qubit-surrenders-110807610.html"},{"credibility":3,"name":"","type":"other","url":"https://www.infosecurity-magazine.com/news/crypto-finance-2m-bug-bounty/"},{"credibility":3,"name":"","type":"other","url":"https://qbt.wiki/en/"},{"credibility":3,"name":"","type":"other","url":"https://tokeninsight.com/en/news/qubit-finance-released-compensation-plan-team-mound-gives-up-all-of-its-tokens-to-compensate-the-community"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://www.coindesk.com/markets/2022/01/28/defi-protocol-qubit-finance-exploited-for-80m"},{"credibility":3,"name":"","type":"other","url":"https://www.cpomagazine.com/cyber-security/hackers-exploited-a-logical-flaw-to-steal-80-million-from-defi-platform-qubit-finance/"},{"credibility":3,"name":"","type":"other","url":"https://www.bankinfosecurity.com/defi-platform-qubit-finance-hacked-for-80-million-a-18406"},{"credibility":3,"name":"","type":"other","url":"https://therecord.media/qubit-finance-platform-hacked-for-80-million-worth-of-cryptocurrency"},{"credibility":3,"name":"","type":"other","url":"https://www.theblock.co/post/132157/qubit-finance-bridge-ethereum-bsc-exploited-lost-80-million"}]}],"sources_used":[],"summary":"Qubit Finance was a Binance Smart Chain lending and cross-chain bridge protocol developed by South Korean firm Mound Inc., the same team behind PancakeBunny. On January 27, 2022, an attacker exploited a logic error in the QBridge Ethereum-BSC bridge to mint approximately 77,162 qXETH tokens without depositing any ETH, then drained roughly $80 million in protocol assets; no funds were ever recovered and the attacker was never identified.","timeline":[{"date":"2021-04-01","event":"Mound Inc. receives $1.6 million seed funding from Binance Labs","source":""},{"date":"2021-05-19","event":"PancakeBunny, Mound Inc.'s other protocol, suffers a $45 million flash loan exploit","source":""},{"date":"2021-11-23","event":"QBridge smart contract first deployed on Binance Smart Chain","source":""},{"date":"2021-11-29","event":"QBridge smart contract first deployed on Ethereum","source":""},{"date":"2022-01-27","event":"Attacker wallet (0xd01ae1a708614948b2b5e0b7ab5be6afa01325c7) funded via Tornado Cash at 9:18 PM UTC","source":""},{"date":"2022-01-27","event":"Attacker submits 16 fraudulent deposit() transactions to QBridge on Ethereum between 9:34 PM and 9:50 PM UTC with zero ETH attached","source":""},{"date":"2022-01-27","event":"BSC relayer processes 16 voteProposal transactions between 9:36 PM and 9:51 PM UTC, minting qXETH for attacker without any real deposit","source":""},{"date":"2022-01-27","event":"Attacker uses minted qXETH as collateral to borrow and extract approximately 206,809 BNB (~$80 million) from the protocol","source":""},{"date":"2022-01-28","event":"Qubit Finance disables all core protocol functions and publicly discloses the exploit","source":""},{"date":"2022-01-28","event":"Qubit team appeals to attacker to return funds, initially offering $250,000 bug bounty","source":""},{"date":"2022-01-29","event":"Qubit team increases bounty offer to $1 million; attacker does not respond publicly","source":""},{"date":"2022-01-31","event":"Bounty offer reported to have been raised to $2 million with no prosecution pledge","source":""},{"date":"2022-02-08","event":"Qubit Finance publishes compensation plan: Team Mound surrenders all tokens to community, commits to debt-funded $10M initial tranche","source":""},{"date":"2022-02-01","event":"Qubit Finance transfers governance authority to community DAO","source":""},{"date":"2022-02-08","event":"Qubit team announces $500,000 bounty for information identifying the attacker, files reports with international law enforcement","source":""},{"date":"2022-01-01","event":"Protocol ceases operations; no funds recovered; attacker never identified or charged","source":""}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision d4f014bf-18a4-4dfe-a34e-60013a09aa2a - #2reviewby reviewerreviewer2026-11-04 00:13:15ZScore: 10 → 10 (no score change)The core exploit facts (date, 77,162 qXETH, ~$80M, Tornado Cash funding, no recovery, $2M bounty) match Rekt and Infosecurity Magazine. The page's closing claims are weaker. 'No longer operational' and 'ceases operations' have no supporting source, and 'compensation never fully executed' conflicts with the project's own reopening and compensation post. The page omits the markets reopening and compensation start. Only a limited sample of claims was checked.anchoranchored
- chain
- ●mainnet-betaslot 465,096,136
- sig
3NGWUYvcmCMT…1JmzW1Amexplorer ↗- hash
4kci9Fk8kjCy…nepp8yvJsha256 → base58
verifying row…full verify ↗canonical bytes (1303 B) ▸
{"actor":"reviewer","artifact_identity":"741c377b04696658e751a22b28c1c27a","decided_at":"2026-11-04T00:13:15.078Z","decision":"review","disputed_pct":0.3333,"findings_hash":"FZnU6HRS49KiVChWD5kQByr9cM7eZvKSS2XEpxEr5uxn","investigation_id":"d90e7a11-4928-45d2-87e7-45da166374d3","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":10,"omissions":{"material":1,"total":1},"page_content_hash":"50beaf8d09699b9c446243a8b1364c7b65e5fd5746651447d3a88e461bfdb455","page_slug":"qubit","prev_score":10,"reason":"The core exploit facts (date, 77,162 qXETH, ~$80M, Tornado Cash funding, no recovery, $2M bounty) match Rekt and Infosecurity Magazine. The page's closing claims are weaker. 'No longer operational' and 'ceases operations' have no supporting source, and 'compensation never fully executed' conflicts with the project's own reopening and compensation post. The page omits the markets reopening and compensation start. Only a limited sample of claims was checked.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":2,"subject_status":"unknown","subject_status_contradicts_page":false,"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 5a079034-c312-4417-8688-f165b9e714f2 - #3review reviseby judgejudge2026-11-04 00:13:15ZScore: 10 → 0 (-18)The core exploit facts (27 Jan 2022 date, 77,162 qXETH minted, about $80M lost, no recovery, $2M bounty) were confirmed against Tier 2 sources (claim_findings[0], [1]). Two of six checked claims, the statements that the protocol 'ceased operations' / is 'no longer operational' (claim_findings[3], [4]), have no supporting source, giving 33% unverifiable. The claim that compensation was never executed (claim_findings[2]) is only partly supported, because the project's own post says markets reopened and compensation would begin in Feb 2022, and the page omits this (omission_findings[0]). The penalty is kept at the lower end of the band because the reviewer's confidence is 0.5 and the key contrary source was seen only as a search snippet.anchoranchored
- chain
- ●mainnet-betaslot 465,096,142
- sig
4cSqT7E871rv…kYriBa2kexplorer ↗- hash
FV7oV5L14ZFv…NczU2tLssha256 → base58
verifying row…full verify ↗canonical bytes (1726 B) ▸
{"actor":"judge","artifact_identity":"741c377b04696658e751a22b28c1c27a","band_override":null,"decided_at":"2026-11-04T00:13:15.078Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"d90e7a11-4928-45d2-87e7-45da166374d3","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":0,"page_slug":"qubit","prev_score":10,"reason":"The core exploit facts (27 Jan 2022 date, 77,162 qXETH minted, about $80M lost, no recovery, $2M bounty) were confirmed against Tier 2 sources (claim_findings[0], [1]). Two of six checked claims, the statements that the protocol 'ceased operations' / is 'no longer operational' (claim_findings[3], [4]), have no supporting source, giving 33% unverifiable. The claim that compensation was never executed (claim_findings[2]) is only partly supported, because the project's own post says markets reopened and compensation would begin in Feb 2022, and the page omits this (omission_findings[0]). The penalty is kept at the lower end of the band because the reviewer's confidence is 0.5 and the key contrary source was seen only as a search snippet.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":-18,"sequence_num":3,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports a material omission (the project's own markets-reopening and compensation post from Feb 2022 is not mentioned) and a high-priority gap on post-2022 status. This confirms the significant band that the percentage already implies."},"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 e6ae830d-7eea-4126-925c-73649fed2fb1
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>.