AFX Bridge
Why it happened
Attack class: Access controlAttackers who had broken into AFX's systems made five hot validators sign one full-balance withdrawal, passing the two-thirds threshold.
What would have stopped it
- Spread validators across independent operators and isolated machines.
- Cap how much the bridge can release per withdrawal and per day.
Not scored before the exploit
BlackHart had not scored AFX Bridge before this exploit.
Attackers drained about $24.15 million in USDC, nearly all of its deposits, from AFX Trade's own custody bridge on Arbitrum. They had spent two weeks inside AFX's systems after tricking a developer with a fake job approach, and used that access to make five of the bridge's validators sign one withdrawal of the full balance. Arbitrum's native bridge and other Arbitrum apps were not affected. The USDC was moved to Ethereum, sold for about 12,467 ETH and later split across about two dozen wallets; AFX's 30% bounty offer went unanswered and it has set up a goodwill program for users instead.
Five compromised validators signed a full-balance withdrawal from the AFX bridge to the attacker wallet, which moved the USDC to Ethereum through a CCTP router, sold it for ETH and sent 12,467 ETH to a consolidation wallet.
Attack flow
All 5 on-chain stepsThe attack in 4 steps. Step 1, Quorum takeover: AFX custody bridge (bridge). Step 2, Release: Attacker wallet (attacker), about $24.15M reached this step. Step 3, Bridge + swap: CCTP to Ethereum, UniswapX to ETH (swap). Step 4, Disperse: Consolidation wallet (exit).
Step 1: Quorum takeover
- BridgeAFX custody bridge24,150,000 USDCalmost all of AFX's deposits0xCb3B9A3E...062e67
Step 2: Release
- AttackerAttacker walletreceives 24.15M USDC at 21:30 UTCafter an unused 200-second dispute window0x2f2974fA...0FEefc
Step 3: Bridge + swap
- SwapCCTP to Ethereum, UniswapX to ETHsix USDC transfers in 11 minutesabout 12,467 ETH0xB3FA262d...DAf3F0
Step 4: Disperse
- ExitConsolidation wallet12,467.44 ETHsplit to about two dozen wallets on July 250x627654B2...b6EBaC
Why each step worked
- Five hot validators signed one full-balance withdrawalabout 71% of voting power against a two-thirds threshold
- One team ran every validatora single intrusion reached enough signers
- No withdrawal size or rate limitmissing controlthe full balance left in one withdrawal
- Nobody watching the dispute windowmissing controlno challenge was filed
- No freeze before conversionmissing controlUSDC became ETH within 12 minutes of release
- Bounty offer unansweredmissing control30% offered for a 70% return
Full forensic detail
Step-by-step reconstruction, root cause, counterfactuals, remediation, and disclosure timeline.
Exploit anatomy
Root cause
AFX Trade, a perpetuals exchange on Arbitrum, kept user USDC in its own custody bridge, which releases funds when validators holding two-thirds of the voting power sign a withdrawal. The bridge contract behaved exactly as written, per Blockaid and CoinDesk, and no contract bug was involved. The failure was operational: the validators that mattered were hot, internet-connected signers run on infrastructure AFX controlled, and a single compromise reached enough of them to pass the threshold. AFX's own account says the intrusion began with a fake recruiter targeting a developer, moved through its build infrastructure, and used an internal management service with privileged access to validator nodes to make a subset of them co-sign the theft. Five signers holding about 71% of the voting power approved one withdrawal for the bridge's full balance. The 200-second dispute window was the only remaining check and nobody used it. AFX said its forensic work is consistent with the North Korea-linked group UNC4899, also called TraderTraitor; zeroShadow and SEAL called the link highly likely but preliminary.
Prevention analysis
One intrusion reached enough validators to pass the threshold because AFX ran them all. Independent operators with separate infrastructure would have forced the attacker to breach several organizations at once.
A single withdrawal took the entire balance. A rate limit would have held the loss to a fraction of the 24.15 million USDC even with the quorum compromised.
The bridge had a 200-second window to object and no one did. Monitoring that disputes any withdrawal above a set size, or a full-balance withdrawal, would have stopped this one.
An internal management service with reach into validator nodes turned a workstation compromise into signing power. Separating signing hosts from everyday infrastructure breaks that path.
Similar incidents
North Korean attackers used a fake job offer to reach five of nine Ronin validator keys and drained about $600 million. Same pattern: a validator set run by one operator falls to one social-engineering breach.
Privileged keys were taken through social engineering and used to move funds with no contract bug involved. Same class: operational security of the people and machines that hold signing power.
An attacker took control of the bridge's validator set and drained about $5.4 million. Same failure point: whoever controls the signing quorum controls the funds.
Remediation
Timeline
Get your protocol scored across 12 dimensions, or request ongoing coverage.