From testing low-cost, long-range precision-strike systems to collecting critical operational data alongside defense industry engineers, this landmark demonstration shows where the Africa Multidomain Training and Experimentation Center is headed.    #AMTEC# #Morroco# @USEmbMorocco

The Aztec Foundation was made aware of a potential exploit targeting Aztec Connect which occurred earlier today, June 14, 2026. There are no links between this product and any smart contracts related to the AZTEC ERC20 token, or current Aztec network. Aztec Connect was deprecated 3 years ago and Aztec Labs retains no controls over the system. Please follow @AztecLabs_ for updates and further information.

🚨SlowMist TI Alert🚨 @aztecnetwork has been exploited again. 💸 Loss: 1,158 ETH+150,000 DAI+0.4696 renBTC (~$2,209,704.23 USD) 🔍 Root Cause: The `RollupProcessor.escapeHatch()` function (`0x737901bea3eeb88459df9ef1be8ff3ae1b42a2ba`) lacks access control: no `onlyOwner`, no `rollupProviders` authorization, and no provider signature verification. When `rollupSize == 0`, the TurboVerifier accepts an escape hatch proof, and `processDepositsAndWithdrawals()` directly trusts the `proofData` public inputs (`publicOutput`, `outputOwner`, `assetId`) without independent validation of fund ownership or withdrawal balance, executing `withdraw(1158 ETH, attacker, 0)`. 📌 Attacker EOA: `0x6952d9246e9afe8b887b2877225163436f78e97f` 📌 Victim Contract: `RollupProcessor` at `0x737901bea3eeb88459df9ef1be8ff3ae1b42a2ba` 📌 Verifier Contract: `TurboVerifier` at `0x48cb7ba00d087541dc8e2b3738f80fdd1fee8ce8` Impact: Attacker drained 1,158 ETH from the `RollupProcessor` by submitting a valid escape hatch proof with spoofed public inputs, exploiting validation in the escape hatch withdrawal path. Powered by #SlowMist#.AI

Mexico at Azteca for the World Cup opener. Altitude advantage. Home crowd. Historic stadium. Now imagine they lose… A certain country starting with B might actually break the internet today. 🤣👇

We're looking for @aztecnetwork sequencers who want to help us improve the sequencing experience. A feedback survey was just posted on the forum, we'd highly appreciate your input!