A reported attack on AFX’s cross-chain bridge on Arbitrum is circulating with a loss figure of about 24.15 million USDC, but the current evidence package narrows confirmation to the cited X status at https://x.com/Ostium/status/2078640436688941194 and the cited explorer record at https://arbiscan.io/tx/0x359f8c05b86a4409d60cfba02084334313fd94b19f74a294fb7fc4ea7d4870e0, rather than a full protocol incident report.
The available sourcing supports a narrow incident notice
The research artifact for this story points readers first to an X post and to an Arbiscan transaction, while the same package says the search process ended early and left no verified-facts array behind. That leaves the headline report publishable only as a claimed bridge exploit affecting AFX on Arbitrum, not as a fully reconstructed hack timeline.
The source list also preserves a USDC reference page, which supports the identity of the asset named in the brief but does not, by itself, prove the route or final scale of the outflow. Until AFX or a security partner publishes a readable statement beyond the cited social reference, the safest framing is that USDC is the token reportedly involved and Arbitrum is the chain named in the incident description.
ON-CHAIN REFERENCE
- Explorer entry: 0x359f8c05b86a4409d60cfba02084334313fd94b19f74a294fb7fc4ea7d4870e0
- Chain named in the brief: Arbitrum
- Use of this record: This is the transaction preserved in the research package; readers need the explorer itself for timestamp, address, and token-flow detail.
What still is not confirmed by the current package
Because the available package does not include extracted text from the X post or decoded transfer details from the Arbiscan entry, this draft cannot verify the exploit path, whether bridge custody logic or permissions failed, or whether the cited transaction represents the entire loss.
That gap matters for users trying to distinguish a protocol-specific failure from a chain-wide issue. The current brief does not contain any source showing core Arbitrum infrastructure was compromised, so readers should treat the event as limited to the reported AFX bridge incident unless future disclosures tied to the explorer record or the initial social post show otherwise.
The next useful evidence should come from AFX, not broader exploit chatter
Coincu has covered other bridge-related incidents, including the Wanchain Cardano BNB bridge attack, TeleSwap’s delayed exploit disclosure and a ZachXBT report tied to bridge flows; what those cases had, and this brief still lacks, is a protocol-side explanation that readers could line up against the on-chain reference.
A separate CoinDesk report on an Ostium exploit appears in the trusted-source list, but it concerns another project and should be read here only as evidence that the source package was assembled around a broader exploit-monitoring workflow, not as independent confirmation of AFX-specific facts.
FAQ about the reported AFX bridge attack
Was Arbitrum itself hacked? The current brief does not include any source showing that, and the only preserved chain-level reference is the single Arbiscan transaction.
How much USDC was reportedly stolen? The report is framed around about 24.15 million USDC, but the brief does not preserve a readable calculation that independently breaks down the amount.
What should affected users watch next? Readers need an AFX statement, a post-mortem, or decoded fund flows tied back to the cited social post and Arbiscan record before firmer conclusions are justified.
Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.
