Fact-check findings

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. #1[disputed][awaiting moderator]in section: ZachXBT Flagging

   “According to reporting based on ZachXBT's Investigations Telegram channel, he traced losses and identified addresses linked to the protocol's treasury multisig and personal wallets.”

   reviewerZachXBT traced losses and identified addresses linked to the protocol's treasury multisig and personal wallets in connection with the Bedrock exploitThe ZachXBT findings belong to the Truflation incident; the page attributes them to Bedrock. The whole section's premise is unsupported.
   Proposed correction (not yet applied)

   The cited cryptonews.net roundup mentions ZachXBT only in connection with a separate incident, the Truflation attack, not the Bedrock exploit.
   citedcryptonews.net/news/security/29852647/
2. #2[disputed][awaiting moderator]in section: ZachXBT Flagging

   “On-chain investigator ZachXBT flagged uniBTC and the Bedrock exploit in connection with his broader analysis of the September 2024 incident.”

   reviewerZachXBT flagged uniBTC/Bedrock exploit in his analysisNo source seen ties ZachXBT to the Bedrock exploit. Recommend removing the section or the sentence. A correction text is not proposed because none is supported.
   citedcryptonews.net/news/security/29852647/www.cryptotimes.io/2024/09/27/bedrock-fa…security-breach/

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

1. #4[unverifiable][awaiting moderator]in section: Smart Contract Exploit — September 2024

   “Stolen funds were subsequently routed through Tornado Cash.”

   reviewerStolen funds routed through Tornado CashPrimary source is silent. The timeline also dates it 2024-09-27, which is a specific date I could not verify.
   citeddedaub.com/blog/bedrock-vulnerability-di…ure-and-actions/
2. #7[unverifiable][awaiting moderator]in the cited sources

   “https://blockonomi.com/bedrock-protocol-reports-2m-exploit-reimbursement-plan-in-progress/”

   reviewerBlockonomi source archive points to an unrelated articleThe stored archive_url path is about a Solana price article, not Bedrock. It does not back the cited claim and should be replaced. I did not fetch the live URL.
   citedblockonomi.com/bedrock-protocol-reports-…lan-in-progress/

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

1. #5[partially supported][awaiting moderator]in section: Insider Threat — Fuzzland Disclosure (June 2025)

   “On or around September 4, 2024, the attacker modified Fuzzland's project `Cargo.toml` file to include a malicious Rust crate named `rands`”

   reviewerFuzzland attributed exploit to former employee using malware in a Rust dependency; Sept 4 date and 'rands' crate; hired as MEV developerCore attribution is supported. The specific crate name, date and one-hour timing were not verified in the sources I could read.
   citedcointelegraph.com/news/fuzzland-ex-emplo…k-unibtc-exploit

The cited evidence supports the claim as written.

1. #3[confirmed][no action needed]in section: Smart Contract Exploit — September 2024

   “At approximately 16:00 UTC on September 26, Dedaub confirmed the vulnerability; at 16:27 UTC it was reported to Bedrock via Twitter; at 16:41 UTC a war room was created on the SEAL 911 platform.”

   reviewerDedaub found the vulnerability and the timeline 16:00/16:27/16:41/18:28 UTCMatches the primary source.
   citeddedaub.com/blog/bedrock-vulnerability-di…ure-and-actions/
2. #6[confirmed][no action needed]in section: Smart Contract Exploit — September 2024

   “Total losses including secondary DEX liquidity pools were estimated at approximately $2 million.”

   reviewerExploit amounts and about $2M totalConsistent across sources.
   citeddedaub.com/blog/bedrock-vulnerability-di…ure-and-actions/