Audit log

Every state-changing event for Meerkat 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.

1. #1publishby system:backfill

   2026-05-22 04:05:27Z
   Score: ? → ? (no score change)
   anchoranchored

   chain

   ●mainnet-betaslot 421,342,885

   sig

   JakD2oZCRz52…V7jN7Z7hcopyexplorer ↗

   hash

   7ndp4Z8kujyR…jVVkwJr8copysha256 → base58

   verifying row…full verify ↗

   canonical bytes (6532 B) ▸

   {"actor":"system:backfill","investigation_id":"57f937cd-6a46-42f9-aa5f-c9b25dcd1cbc","kind":"publish","page_slug":"meerkat-finance","published_at":"2026-05-22T04:05:27.237Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Meerkat Finance","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://bscscan.com/token/0xc65f62d372aa50e99b2a564ddb418a6bc84faa15","type":"other","url":""},{"credibility":3,"name":"https://cointelegraph.com/news/binance-smart-chain-copykat-project-loses-31-million-in-possible-rugpull","type":"other","url":""},{"credibility":3,"name":"https://rekt.news/meerkat-finance-bsc-rekt","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://rekt.news/meerkat-finance-bsc-rekt","type":"other","url":""},{"credibility":3,"name":"https://hackmd.io/@mLAPku2WQZmso5oX4kzPOg/BkNlZv0zO","type":"other","url":""},{"credibility":3,"name":"https://www.vidma.io/blog/meerkat-finance-anatomy-of-a-31-million-defi-rug-pull-on-binance-smart-chain","type":"other","url":""},{"credibility":3,"name":"https://beincrypto.com/defi-project-meerkat-suspected-of-31-million-rug-pull/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.coindesk.com/policy/2021/03/04/defi-project-meerkat-raises-eyebrows-with-claimed-31m-hack-a-day-after-launch","type":"other","url":""},{"credibility":3,"name":"https://cointelegraph.com/news/binance-smart-chain-copykat-project-loses-31-million-in-possible-rugpull","type":"other","url":""},{"credibility":3,"name":"https://rekt.news/meerkat-finance-bsc-rekt","type":"other","url":""},{"credibility":3,"name":"https://beincrypto.com/defi-project-meerkat-suspected-of-31-million-rug-pull/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://cointelegraph.com/news/dev-says-31-million-meerkat-finance-exploit-was-a-test-will-return-funds","type":"other","url":""},{"credibility":3,"name":"https://www.thedechained.com/meerkat-finance-exploit-was-a-trial-jamboo/","type":"other","url":""},{"credibility":3,"name":"https://web3isgoinggreat.com/?id=2021-03-04-0","type":"other","url":""},{"credibility":3,"name":"https://www.quadrigainitiative.com/casestudy/meerkatfinancerugpull.php","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.binance.com/en/blog/421499824684901829/How-Binance-Security-team-helped-recover-$30M-funds-from-Meerkat-Finance-Hack","type":"other","url":""},{"credibility":3,"name":"https://www.cryptohopper.com/news/how-binance-security-team-helped-recover-30m-funds-from-meerkat-finance-hack-3026","type":"other","url":""},{"credibility":3,"name":"https://coincodex.com/article/10890/how-binance-security-team-helped-recover-30m-funds-from-meerkat-finance-hack/","type":"other","url":""},{"credibility":3,"name":"https://www.quadrigainitiative.com/casestudy/meerkatfinancerugpull.php","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://u.today/largest-binance-smart-chain-fraud-meerkat-finance-mkat-rug-pulled-with-32-million-losses","type":"other","url":""},{"credibility":3,"name":"https://decrypt.co/62204/binance-smart-chain-hit-by-2-4-million-turtledex-exit-scam","type":"other","url":""},{"credibility":3,"name":"https://www.merklescience.com/blog/diving-into-defi-aeu-crypto-crime-in-defi","type":"other","url":""},{"credibility":3,"name":"https://rekt.news/meerkat-finance-bsc-rekt","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://cointelegraph.com/news/dev-says-31-million-meerkat-finance-exploit-was-a-test-will-return-funds","type":"other","url":""},{"credibility":3,"name":"https://www.coindesk.com/policy/2021/03/04/defi-project-meerkat-raises-eyebrows-with-claimed-31m-hack-a-day-after-launch","type":"other","url":""},{"credibility":3,"name":"https://www.quadrigainitiative.com/casestudy/meerkatfinancerugpull.php","type":"other","url":""}]}],"sources_used":[],"summary":"Meerkat Finance was a Binance Smart Chain yield-vault protocol that launched on March 3, 2021 and was drained of approximately $31.56 million in BUSD and BNB less than 24 hours later. On-chain evidence indicates the project's own deployer address executed the exploit, pointing to an intentional exit scam rather than an external hack. A developer identifying as 'Jamboo' subsequently claimed the drain was a 'trial' testing user greed, promised full refunds, and approximately 95% of funds were eventually recovered under heavy pressure from Binance and the BSC community.","timeline":[{"date":"2021-03-03","event":"Meerkat Finance launches on Binance Smart Chain at approximately 19:00 UTC. The protocol attracts over $31 million in user deposits within 24 hours.","source":""},{"date":"2021-03-04","event":"At 08:53:10 UTC, the Meerkat Finance deployer upgrades the WBNB Vault to a malicious contract. At 08:53:31 UTC, the BUSD Vault is similarly upgraded. By 08:54:55 UTC, 13,968,039 BUSD and 73,635 WBNB (totaling approximately $31.56 million) are drained from both vaults.","source":""},{"date":"2021-03-04","event":"Meerkat Finance's website, Twitter account, and GitHub repositories are taken offline. Cached copies are removed from Wayback Machine and Google Cache. The Binance.org Bridge is suspended to prevent cross-chain movement of stolen funds.","source":""},{"date":"2021-03-04","event":"Binance announces it will freeze any stolen funds that reach its exchange. Binance engages PeckShield, SlowMist, and CertiK to assist in the investigation.","source":""},{"date":"2021-03-05","event":"A developer using the pseudonym 'Jamboo' posts in a new Telegram channel ('Meerkatrefunds') claiming the exploit was a 'trial' testing user greed. Jamboo confirms association with the project by sending a transaction from the deployer address and promises full refunds.","source":""},{"date":"2021-03-06","event":"A refund smart contract is deployed. Victims are required to interact with the contract directly to reclaim their funds.","source":""},{"date":"2021-03-07","event":"Approximately 95% of user funds (~$30 million) are reported as recovered, with ongoing distributions to remaining victims. Binance describes the outcome as the largest fund recovery it has participated in.","source":""}]},"v":1}

   Verify offline (run on your own machine)

   python -m src.verify_decision ac2c784e-81ac-4bef-bea7-4b9da6e59a09copy
2. #2rescoreby systemsystem

   2026-10-27 06:03:33Z
   Score: 4 → 0 (-4)
   Rescored under Scoring v2, the published formula (avoid.net/scoring): 4 → 0. The page establishes that the subject is itself a scheme, so the score is 0.
   anchoranchored

   chain

   ●mainnet-betaslot 461,963,152

   sig

   23ks5qgTKUT1…cgGtTuDRcopyexplorer ↗

   hash

   43FZTgHcdbTq…hffJXXmpcopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (521 B) ▸

   {"actor":"system","decided_at":"2026-10-27T06:03:33.301Z","decision":"rescore","investigation_id":"57f937cd-6a46-42f9-aa5f-c9b25dcd1cbc","new_score":0,"page_slug":"meerkat-finance","prev_score":4,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 4 → 0. The page establishes that the subject is itself a scheme, so the score is 0.","score_delta":-4,"score_model":"v2","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 53dc688e-2a52-4e95-a15f-6c500c2f4b4ccopy
3. #3reviewby reviewerreviewer

   2026-11-02 00:23:15Z
   Score: 0 → 0 (no score change)
   The core incident narrative (launch on March 3, 2021, deployer-executed vault upgrades on March 4, about $31M drained, the Jamboo 'trial' claim, refund program, about 95% recovery) is supported by the sources checked. Problems are the Jamboo post date (March 5 on the page, March 6 in sources), a dead Binance blog URL, timeline dates for the refund contract and recovery that appear unsupported, and Binance bridge suspension and security-firm claims not found in the cited article. Timeline entries have no source fields. Only a subset of sources was fetched.
   anchoranchored

   chain

   ●mainnet-betaslot 464,292,298

   sig

   WfJiStbZ4k5n…1Q5JKh6acopyexplorer ↗

   hash

   FrVqAUdcz67k…P1SpQc7ccopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (1377 B) ▸

   {"actor":"reviewer","artifact_identity":"d4a46b67786a726cf465473519e9ef6a","decided_at":"2026-11-02T00:23:14.973Z","decision":"review","disputed_pct":0.4444,"findings_hash":"3SCkxzsXS4dz3RU2JmLkGNCmNRTdwQ1spxxcETFzqDEE","investigation_id":"57f937cd-6a46-42f9-aa5f-c9b25dcd1cbc","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_content_hash":"ea14d6388b8d59b6eb57286c870002ec3d1f14aee557e768707e883fb735c9b9","page_slug":"meerkat-finance","prev_score":0,"reason":"The core incident narrative (launch on March 3, 2021, deployer-executed vault upgrades on March 4, about $31M drained, the Jamboo 'trial' claim, refund program, about 95% recovery) is supported by the sources checked. Problems are the Jamboo post date (March 5 on the page, March 6 in sources), a dead Binance blog URL, timeline dates for the refund contract and recovery that appear unsupported, and Binance bridge suspension and security-firm claims not found in the cited article. Timeline entries have no source fields. Only a subset of sources was fetched.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"shut_down","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 04d37080-faed-462b-a1e4-f86798a64dd3copy
4. #4review reviseby judgejudge

   2026-11-02 00:23:15Z
   Score: 0 → 0 (no score change)
   Of 9 claims checked, 1 was disputed (claim_findings[1], the Jamboo post dated March 5 where sources say March 6) and 3 could not be verified (claim_findings[5], [7], [8]: the Binance bridge and security-firm claims, the 19:00 UTC launch hour, and the no-audit claim), giving 44%, which falls in the significant-issues band. The core incident account is confirmed (claim_findings[0], [2], [4]): the deployer executed the vault upgrades, about $31M was drained, and the Jamboo 'trial' statement and roughly 95% recovery match sources. The Binance blog link is dead (claim_findings[3]), and the 2021-03-07 recovery date and 2021-03-06 refund contract date are unsupported (claim_findings[6]). Because the disputed and unverified items are mostly secondary details, reviewer confidence is moderate (0.6), and no omissions were found, the penalty is set at the mild end of the band.
   anchoranchored

   chain

   ●mainnet-betaslot 464,292,303

   sig

   5jAihPTHGDEB…dJdFDkoPcopyexplorer ↗

   hash

   CHGYRoayxyh5…aRUzpQcLcopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (1524 B) ▸

   {"actor":"judge","artifact_identity":"d4a46b67786a726cf465473519e9ef6a","band_override":null,"decided_at":"2026-11-02T00:23:14.973Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4444,"investigation_id":"57f937cd-6a46-42f9-aa5f-c9b25dcd1cbc","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"meerkat-finance","prev_score":0,"reason":"Of 9 claims checked, 1 was disputed (claim_findings[1], the Jamboo post dated March 5 where sources say March 6) and 3 could not be verified (claim_findings[5], [7], [8]: the Binance bridge and security-firm claims, the 19:00 UTC launch hour, and the no-audit claim), giving 44%, which falls in the significant-issues band. The core incident account is confirmed (claim_findings[0], [2], [4]): the deployer executed the vault upgrades, about $31M was drained, and the Jamboo 'trial' statement and roughly 95% recovery match sources. The Binance blog link is dead (claim_findings[3]), and the 2021-03-07 recovery date and 2021-03-06 refund contract date are unsupported (claim_findings[6]). Because the disputed and unverified items are mostly secondary details, reviewer confidence is moderate (0.6), and no omissions were found, the penalty is set at the mild end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","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 0d4c06f8-993e-4bb4-be1f-7a9b38e588f4copy