AFX Cross-Chain Bridge on Arbitrum was attacked and 24.15 million USDC was stolen

AFX's cross-chain bridge on Arbitrum was attacked and approximately 24.15 million USDC were stolen.

It is alleged that AFX's cross-chain bridge on Arbitrum was attacked, resulting in approximately 24.15 million USDC losses. However, the current evidence package can only confirm the cited social platform posts and blockchain browser records, rather than a complete protocol incident report.

Existing sources only support limited event notifications

The research material for this article first guides readers to view a social platform post and an Arbiscan transaction record, while the material package states that the search process ended prematurely, leaving no verified facts. Therefore, this headline report can only be used as a purported bridging vulnerability incident involving AFX on Arbitrum, rather than a complete restoration of the attack timeline.

A USDC reference page is also retained in the source list to confirm the identity of the assets mentioned in the briefing, but this page alone cannot prove the path or final size of the capital outflow. Before AFX or security partners issue a readable statement other than the social quote above, the safest way to state it is: USDC is the token allegedly involved, and Arbitrum is the chain mentioned in the event description.

On-chain reference

Browser record: 0x359 f8c05 b86a4409d 60cfba 02084334313 fd94 b19f74a294fb7fc 4ea7 d4870e0

Chain mentioned in the briefing: Arbitrum

Purpose of this record: This is the transaction stored in the research package; readers need to view the timestamp, address and token flow details through their own browser.

Information that has not yet been confirmed in the current package

Since the existing material package does not contain the extracted text of social platform posts and does not decode the transfer details in the Arbiscan entry, this draft cannot verify whether the vulnerability path, bridge custody logic or permissions are invalid. Or whether the transaction cited represented a full loss.

This gap is critical for users trying to distinguish protocol-specific faults from chain-wide issues. There are no sources in the current briefing indicating a breach of core Arbitrum infrastructure, so readers should view this incident as limited to the reported AFX bridging incident, unless future disclosures related to browser records or initial social posts indicate otherwise.

The next useful evidence should come from the AFX rather than the broader vulnerability discussion

Bridge-related incidents have been reported in other media, but what these cases have, and what is still missing in this brief, is the explanations given by the parties to the agreement. Readers can compare it with on-chain references. Another report of a vulnerability in other projects appears on the list of trusted sources, but the report concerns another project and is used here only as a source package of evidence gathered around a broader vulnerability monitoring workflow, rather than as an independent confirmation of specific facts about AFX.

Frequently asked questions about reported AFX bridging attacks

Was the Arbitrum itself hacked?

The current briefing does not include any sources that indicate this, and the only chain-level reference retained is a single Arbiscan transaction.

What was the amount of USDC allegedly stolen?

The report revolves around approximately 24.15 million USDC, but the briefing does not retain a readable calculation process that can independently decompose the amount.

What should affected users focus on next?

Readers will need to wait for AFX's statement, post-mortem analysis report, or decoded funding flows associated with cited social posts and Arbiscan records before reaching more precise conclusions.

Disclaimer : This article is for reference only and does not constitute financial or investment advice. There are significant risks in the cryptocurrency and digital asset markets. Before making a decision, be sure to study it yourself.