Skip to main content
AVOID.NET
← Aztec Connect Deprecated Bridge Exploits (June 2026)reviewed 2026-10-27 · 10 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Aztec Connect Deprecated Bridge Exploits (June 2026) against the sources the page cites. Only the most recent review is shown.

Read this first

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.

unverifiable 2partially supported 4confirmed 40 corrections pending · 0 applied

unverifiable

2 claims

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

  1. #9[unverifiable][awaiting moderator]in section: Background: Aztec Connect, the Private Rollup Bridge and Deprecation
    “The Aztec Foundation described it as a 'Stage 2 rollup' deprecated in 2022.”
    reviewerAztec Foundation described the bridge as a 'Stage 2 rollup' deprecated in 2022The X post could not be read without login; the 'Stage 2 rollup' wording was not found in the CoinJournal article or the search results.
  2. #10[unverifiable][awaiting moderator]in section: Combined Losses and Systemic Risk of Immutable Legacy Contracts
    “CoinTelegraph and Crypto Briefing reported that about $44 million was stolen across several protocols in this period, including an alleged $30 million loss at Humanity Protocol and an $8 million compromise of the Syscoin Bridge.”
    reviewerBroader context: about $44M stolen incl. $30M at Humanity Protocol and $8M Syscoin Bridge; Protos over $340M cumulativeNot checked in a fetched source; the figures were not found in searches. Not scored beyond this.

partially supported

4 claims

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

  1. #4[partially supported][awaiting moderator]in section: First Exploit: Aztec Connect Rollup Contract (June 14, 2026)
    “describes them being moved through a chain of disposable wallets (0x7ec9...06db to 0xc431...c1f5 to 0x0af7...9912) and then to a high-volume service contract at 0xd90e...f31b”
    reviewerFund movement through disposable wallets to a high-volume service contractAddresses are right, but the post-mortem attributes this routing to the second-wave actor. The page's sentence reads as if it concerns the first attacker's funds. Wording is hedged.
  2. #5[partially supported][awaiting moderator]in section: Follow-on Residual Drain of Aztec Connect (June 15, 2026)
    “Together with the June 14 attack, total Aztec Connect losses were approximately $2.27 million.”
    reviewerTotal Aztec Connect losses were approximately $2.27 millionThe post-mortem states no $2.27M total. Summing its own figures gives about $2.28M, so $2.27M is a derived approximation off by about $10k.
  3. #6[partially supported][awaiting moderator]in the timeline
    “June 18: combined losses reported at about $4.25M or more; no funds recovered; AZTEC token falls about 1.6%.”
    reviewerTimeline: combined losses about $4.25M; AZTEC token falls about 1.6% (sourced to CoinJournal / Coinpedia)The cited CoinJournal article does not report the 1.6% token move. The $4.25M sum is consistent with its components. The price figure was not verified in the cited source.
  4. #7[partially supported][awaiting moderator]in section: Second Exploit: Aztec Private Rollup Bridge escapeHatch (June 17–18, 2026)
    “CertiK confirmed the incident, and SlowMist and BlockSec published analyses.”
    reviewerSecond exploit June 17-18 via escapeHatch, about $2.16-2.21M, CertiK flaggedCertiK flagging is confirmed. SlowMist and BlockSec analyses of the second exploit were not verified (the Crypto Times source returned 403).

confirmed

4 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: First Exploit: Aztec Connect Rollup Contract (June 14, 2026)
    “At approximately 12:26 UTC on June 14, 2026, an attacker drained approximately $2.19 million from the deprecated Aztec Connect RollupProcessor (RollupProcessorV3) contract”
    reviewerFirst exploit on June 14, 2026 at about 12:26 UTC drained about $2.19M from Aztec ConnectTime, date and amount match the Aztec Labs post-mortem.
  2. #2[confirmed][no action needed]in section: Background: Aztec Connect, the Private Rollup Bridge and Deprecation
    “Aztec Labs' incident post states that all administrative roles and upgrade authority were renounced on-chain in April 2024, after about one year of advance notice to users.”
    reviewerAdmin roles and upgrade authority renounced on-chain in April 2024 after about a year of noticePage correctly flags that other outlets differ.
  3. #3[confirmed][no action needed]in section: Technical Root Cause: Public Input Binding Flaws
    “rollups were submitted with numRealTxs=1 but 2 rows, so the proof validated both rows while settlement processed only row 0”
    reviewernumRealTxs=1 with 2 rows mechanismConsistent with the official post-mortem and search summaries.
  4. #8[confirmed][no action needed]in section: Scope: Current Aztec Network
    “Aztec Labs and the Aztec Foundation said neither the current Aztec Network nor the AZTEC ERC-20 token is connected to, or was affected by, the exploited contracts”
    reviewerNeither exploit involved key compromise; Aztec Foundation statements; no linkage to current networkMatches the Foundation statement as quoted by CoinJournal and the search results.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.