Digital Asset
Intelligence
Theme

Search 3CBlock

News, exchanges, regulatory intelligence, reviews and Voices.

Security Incident · Bridge

CrossCurve Smart Contract Vulnerability: $3M Reported Loss

Historical incident record

Incident Overview

The cross-chain liquidity protocol CrossCurve (formerly EYWA) has confirmed that its cross-chain bridge protocol is under attack, due to a vulnerability in its smart contract that was exploited, resulting in the theft of approximately USD 3 million across multiple networks. Blockchain security firm Defimon Alerts identified that the attack vector exploited a gateway verification bypass vulnerability in CrossCurve’s ReceiverAxelar contract. Analysis shows that anyone could use a forged cross-chain message to call the contract’s expressExecute function, thereby bypassing the intended gateway verification and triggering unauthorized token unlocks on the protocol’s PortalV2 contract. Subsequently, CrossCurve issued a security update regarding the $EYWA token, stating that the exploitation has been successfully contained.

Sources & References

This record presents information attributed to the linked sources. Incident dates describe the original event, not a new report. Reported loss figures reflect the source record and are not current market valuations.

More Security Incidents

View All →
  1. Incident date
    Target

    Unleash Protocol

    Attack methodPrivilege compromise
    Reported loss$ 3,900,000
  2. Incident date
    Target

    Stake DAO

    Attack methodSmart Contract Vulnerability
    Reported loss$ 176,000
  3. Incident date
    Target

    Kelp DAO

    Attack methodSupply Chain Attack
    Reported loss$ 293,000,000
  4. Incident date
    Target

    ZetaChain GatewayEVM

    Attack methodSmart Contract Vulnerability
    Reported loss$ 334,000
  5. Incident date
    Target

    Sweat Foundation

    Attack methodSmart Contract Vulnerability
    Reported loss$ 3,500,000
  6. Incident date
    Target

    Arbitrum Governance

    Attack methodThe X account was hacked
    Reported lossNot disclosed
  7. Incident date
    Target

    Step Finance

    Attack methodPrivate Key Leakage
    Reported loss$ 40,000,000