CrossCurve Hack

TOTAL LOST $3.0M
Medium Spoofed Cross-Chain Messages / Other

Summarize with AI

Affected Chain 2026 Incident surface
Recovered - No recovery reported
All-Time Rank #548 By amount stolen
Auditors 3 Prior security audits

Incident Overview

On February 1, 2026, CrossCurve bridge suffered a ~$2.9M exploit across multiple chains when an attacker exploited an authorization bypass vulnerability in the ReceiverAxelar contract.

The vulnerability existed in the ReceiverAxelar contract's expressExecute() function, which bypassed Axelar's intended security model. In the proper flow, cross-chain messages must be approved by the Axelar Gateway and validated via validateContractCall(), binding specific parameters to authorized execution. However, expressExecute() skipped this validation entirely and relied only on peer checks using attacker-controlled sourceChain and sourceAddress parameters.

The attacker exploited this by submitting spoofed messages, taking the receiveData branch, and executing arbitrary payloads that triggered unlock() on the Eywa CLP Portal, releasing cross-chain assets without authorization. The team discovered an additional $140,762 stolen via bot-driven attacks during investigation, bringing total losses to approximately $2.9M. CrossCurve issued a 72-hour ultimatum to addresses holding exploited funds, offering 10% bounty under SafeHarbor WhiteHat policy for returns, threatening legal action, exchange freezes, and law enforcement collaboration if funds aren't returned.

Incident Report

Protocol / Project CrossCurve
Date of Incident
Attack Technique Spoofed Cross-Chain Messages / Other
Classification Protocol Logic / Bridge
Primary Source View Post-Mortem

Protocol Information

Protocol Type Cross Chain Bridge
Official Website crosscurve.fi/
Protocol Twitter/X @crosscurvefi
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Decentralized Finance (DeFi) Fantom Ecosystem

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Deep understanding of spoofed cross-chain messages / other and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in CrossCurve's contract logic - root cause: protocol logic / bridge
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Likely — with a thorough Spoofed Cross-Chain Messages / Other audit checklist and test coverage
Audited by Audit Report 1, Audit Report 2, Audit Report 3 — still lost $3.0M. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to CrossCurve, these are the critical security checks that could have prevented this incident (February 2026).

  • Verify all logic paths related to Spoofed Cross-Chain Messages / Other are guarded by proper access controls and input validation
  • Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Security Audit History

Sources & References

Learn to Prevent the Next CrossCurve

The CrossCurve hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Recreate exploit patterns safely Free Trial