Briefing
The FEG Token Bridge was compromised via a critical flaw in its cross-chain message verification logic, allowing an attacker to execute unauthorized withdrawals across multiple chains. This exploit bypassed the intended security checks, leading to the theft of FEG tokens which were immediately swapped for native assets. The primary consequence is a direct $1 million USD loss, highlighting the systemic fragility of custom-built interoperability solutions.
Context
The prevailing risk factor for cross-chain protocols remains the security of the message passing layer, as custom implementations often introduce novel attack surfaces not covered by standard smart contract audits. This particular bridge, while leveraging the Wormhole infrastructure for communication, introduced a proprietary verification process that became the single point of failure. The reliance on an unverified relayer contract for whitelisting was a known class of architectural risk in bridge designs.
Analysis
The attacker exploited an error in the FEG relayer contract’s logic, which failed to adequately verify the sourceAddress of a cross-chain message. By sending a malicious message that designated the attack contract as an ‘admin’ and the sourceAddress as the attack contract, the attacker successfully added their contract to the bridge’s whitelist. This whitelist bypass rendered subsequent security checks ineffective, allowing the attacker to call the token withdrawal function and drain approximately $1 million USD in FEG tokens across Ethereum, Base, and BSC.
Parameters
- Total Loss (USD) → $1,000,000; Approximate total value of stolen tokens across three chains.
- Attack Vector → Cross-chain message verification flaw; The root cause was an error in the bridge’s custom message verification process.
- Affected Chains → Ethereum, Base, and BSC; The exploit was executed across all three chains managed by the bridge.
- Stolen Assets → FEG tokens, ETH, and BNB; FEG tokens were withdrawn and immediately swapped for native chain assets.
Outlook
Users must immediately cease all interaction with the compromised bridge and await an official post-mortem and remediation plan from the development team. This incident will likely trigger a renewed focus on standardized, formally verified cross-chain communication protocols, increasing the pressure on all custom bridge implementations to undergo rigorous, third-party security reviews of their message verification logic. The immediate second-order effect is a heightened contagion risk for any protocol using similar whitelisting or custom relayer logic for cross-chain asset transfers.
Verdict
This exploit confirms that bespoke cross-chain message verification logic is a critical, high-value attack surface that mandates immediate, industry-wide re-auditing and a shift toward trustless, standardized interoperability primitives.
