The Arbitrum AFX Bridge was reportedly hacked for about $24.15 million in USDC, according to early social-media reports that had not been independently verified at the time of writing. The claim describes a possible cross-chain bridge exploit on Arbitrum, but the central details remained unconfirmed at press time.

Cross-chain bridges have been among the most frequently targeted categories of decentralized-finance infrastructure, largely because they hold pooled assets locked on one chain to mint or unlock representations on another, creating a concentrated store of value that attackers can attempt to exploit through vulnerabilities in smart-contract logic, validator signatures, or message-passing mechanisms.

The reported incident concerns an AFX-branded bridge on the Arbitrum network, with the alleged stolen funds denominated in USDC. The allegation circulated through an account on X, but it has not been matched with an official statement from the protocol or an affiliated team.

The research file supporting the report is marked partial rather than fully verified. That distinction is important: both the reported amount and the existence of the exploit currently rely on a single reported source. The figures should therefore be treated as allegations pending official and on-chain confirmation.

Coverage of the same event has also begun to appear elsewhere, including a report that the AFX Trade bridge exploit on Arbitrum drained roughly $24 million in USDC. Similar figures appearing across outlets should be treated as consistent reporting, not independent verification, until a public on-chain trail is available.

What is confirmed and what remains unverified

No independently verified facts were captured in the research file behind this article. At the time of writing, there was no confirmed transaction hash, attacker address, or protocol acknowledgment on record.

Readable supporting sources were not assembled, and no market data, expert commentary, or regulatory context was verified for the incident. Wallet addresses, exploit mechanics, and any attribution of the attacker are being omitted because none of those details could be sourced.

This is not the first security concern involving the network. Arbitrum has previously seen protocol-level exploit reports, including the Ostium vault exploit tied to oracle manipulation, a context that helps explain why bridge and smart-contract incidents on the chain draw rapid attention.

What would be needed to confirm the report

The recommended editorial handling of this story is to hold and reframe rather than amplify, because the current evidence base is thin. Several specific confirmations would materially strengthen the report.

The first would be an official statement from the AFX bridge team or a linked protocol acknowledging or denying the incident.

The second would be on-chain proof, meaning a verifiable transaction trail on Arbitrum's block explorer showing the movement of funds and identifying the attacker address.

The third would be clear fund status, including whether the reported USDC has been bridged out, swapped, or frozen. Because USDC is an issuer-backed stablecoin, its issuer Circle operates an on-chain freeze function that can lock specific addresses, a mechanism that has been used in past exploit recoveries. Whether that capability would apply here depends on identifying the receiving address and on the funds remaining on a chain where the freeze is enforceable.

If the incident is confirmed, the next question would be operational scope: whether deposits, withdrawals, or general bridge functionality have been paused or affected for users. Those details would determine whether the report describes an isolated drain or an ongoing risk.

Context sources for the broader network, such as Arbitrum's token market page, do not themselves substantiate the exploit claim and are useful only for framing, not confirmation. Bridge and product risk has remained a recurring issue across the sector, including in recent reporting on BitMEX delisting 65 trading pairs and contracts in July.

Until a protocol statement, an on-chain trail, and a clear fund status are published, the reported loss should be treated as an unconfirmed allegation rather than an established event. The story will be updated as verifiable information becomes available.