Blockchain security firm Blockaid has reported that an AFX-operated bridge suffered a $24.15 million loss in USDC following an exploit, according to a post on X. However, the public record supporting that claim remains limited, with the cited social media post serving as the primary supporting document at the time of publication. Cross-chain bridges — services that move assets between different blockchains — have been a recurring focal point for security incidents in decentralized finance, with several high-profile exploits drawing attention to the operational and smart-contract risks associated with bridged value transfer.

Based on the available material, the narrowest confirmed details are that the reported loss involved USDC and that the affected service was described as an AFX-operated bridge. The cited X post does not supply wallet addresses, a contract identifier, a bridge pause notice, or a block explorer link that would allow independent tracing of any related fund movement.

Several routine verification points remain unanswered. The public post does not indicate the timestamp of the alleged drain, whether the reported outflow occurred in a single transfer or multiple transactions, or which address first received the USDC. Without an attached public record beyond the cited post, the exploit path, the destination of any outflow, and whether recovery or containment action has commenced cannot be independently verified.

The current status of the affected bridge — whether it remains live, paused, or restricted to certain transfers — is also unclear. The available X material does not include user guidance, reimbursement language, or any technical description of how the suspected exploit was executed.

Bitcoin Info News has separately reported on the NIGHT Bridge exploit, the Balance Coin plunge following a suspected exploit, and the SecondFi wallet breach. In the AFX case, the current evidence resolves back to a single cited X post rather than to a fuller operator thread or on-chain disclosure.

The next meaningful confirmation would require an official AFX statement, a named contract, or an explorer page tied to the reported loss. None of those items appear in the cited material, meaning any stronger claim about user impact, chain exposure, or remediation would go beyond the evidence currently available. As with prior bridge-related incidents, the absence of timely on-chain corroboration or operator disclosure has historically slowed independent verification and left affected users awaiting official guidance.

Additional source references: source document 1, source document 2.