Fact-check findings
What an automated fact-checker found when it re-read B² Network (BSquared) — Bitcoin Layer-2 Staking Contract Exploit against the sources the page cites. Only the most recent review is shown.
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.
partially supported
2 claimsThe cited evidence supports part of the claim but not all of it.
- #4[partially supported][awaiting moderator]in section: Fund Movement and Laundering Path
“then bridged the proceeds to Ethereum.”
reviewerFund movement: swapped to ~5,409 WBNB, bridged to Ethereum, NEAR Intents/HOT, Zcash intent; accounts divergeSubstance supported and hedged; the page names PeckShield and Specter while edgeX also cites Lookonchain. Minor attribution blur. - #6[partially supported][awaiting moderator]in section: Market Impact
“with one outlet citing a decline of approximately 44% before a partial recovery.”
reviewerB2 token fell ~44% before partial recoveryFigures vary across outlets (15%, 40%, 44%); the page already flags single-source status.
confirmed
4 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: The Exploit
“On-chain analysts reported that the attacker drained approximately 8.591 million B2 tokens, valued at roughly $3.86 million at the time, from the BNB Chain-based staking contract.”
reviewerAttacker gained unauthorized access to the staking contract's upgrade authority and drained about 8.591M B2 (~$3.86M)Figures and mechanism match the secondary sources. - #2[confirmed][no action needed]in section: The Exploit
“Some analysts suggested the privileged wallet used in the attack had held upgrade-authority access since 2025”
reviewerPrivileged wallet held upgrade authority since 2025; insider/compromised credential suggested by analystsAppropriately hedged. - #3[confirmed][no action needed]in section: Project Response and Leniency Offer
“The team also issued an on-chain leniency offer: if the attacker returned at least 10% of the stolen funds (approximately $386,000) to a designated address within 24 hours, the project said it would not pursue legal action, framing the offer as a goodwill gesture.”
reviewerProject suspended staking, pledged compensation, Discord unstaking, 10% leniency offer within 24 hoursMatches. The 'deadline passed without confirmation' statement is a hedged absence claim; no contrary report found. - #5[confirmed][no action needed]in section: Combined Losses Across Three Unrelated Incidents on the Same Day
“Secondary coverage summed the three incidents to a combined loss of approximately $35.55 million, attributing the individual loss estimates to security firms Blockaid and PeckShield.”
reviewerSame-day AFX (~24.15M USDC, Blockaid 21:30 UTC July 22) and VerusCoin (~$7.55M, Tornado Cash) exploits; combined ~$35.55MConfirmed. Page's cautious Lookonchain note is appropriate.