Incident Score: Analysis & Impact (CURCRO1770021757)
The details regarding individual company incidents & reports gives you full view from every side.
Rankiteo Score Impact Analysis
Key Highlights From The Incident Analysis
- Timeline of CrossCurve's Cyber Attack and lateral movement inside company's environment.
- Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
- How Rankiteo’s incident engine converts technical details into a normalized incident score.
- How this cyber incident impacts CrossCurve Rankiteo cyber scoring and cyber rating.
- Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.
Full Incident Analysis Transcript
In this Rankiteo incident briefing, we review the CrossCurve breach identified under incident ID CURCRO1770021757.
The analysis begins with a detailed overview of CrossCurve's information like the linkedin page: https://www.linkedin.com/company/crosscurvefi, the number of followers: 1782, the industry type: IT Services and IT Consulting and the number of employees: 23 employees
After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 749 and after the incident was 710 with a difference of -39 which is could be a good indicator of the severity and impact of the incident.
In the next step of the video, we will analyze in more details the incident and the impact it had on CrossCurve and their customers.
On 31 January 2024, CrossCurve (formerly EYWA) disclosed Smart Contract Exploit issues under the banner "CrossCurve Bridge Exploit Drains $3 Million in Multi-Chain Cyberattack".
CrossCurve, a cross-chain decentralized exchange and liquidity protocol formerly known as EYWA, suffered a major cyberattack on January 31 after attackers exploited a smart contract vulnerability, draining approximately $3 million across multiple blockchain networks.
The disruption is felt across the environment, affecting Cross-chain decentralized exchange and liquidity protocol, plus an estimated financial loss of $3 million.
In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like Urged users to halt all interactions with the protocol, and stakeholders are being briefed through Public disclosure and advisories.
The case underscores how Ongoing, teams are taking away lessons such as The breach demonstrated that a single vulnerable smart contract could compromise the entire system, regardless of layered validation. Reinforces concerns over bridge security in decentralized finance, with advisories going out to stakeholders covering Curve Finance advised users with exposure to EYWA-related pools to review their positions.
Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.
The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.
MITRE ATT&CK® Correlation Analysis
Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Exploit Public-Facing Application (T1190) with high confidence (90%), supported by evidence indicating exploited a smart contract vulnerability in ReceiverAxelar contract. Under the Execution tactic, the analysis identified Serverless Execution (T1648) with high confidence (90%), supported by evidence indicating attackers called expressExecute function with forged data to trigger unauthorized token unlocks. Under the Defense Evasion tactic, the analysis identified Code Signing (T1553.002) with moderate to high confidence (80%), supported by evidence indicating bypassed gateway security using spoofed cross-chain messages and Exploitation for Defense Evasion (T1211) with high confidence (90%), supported by evidence indicating lacked a critical validation check in ReceiverAxelar contract. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Bash History (T1552.003) with moderate to high confidence (70%), supported by evidence indicating unauthorized token unlocks via PortalV2 contract without proper authorization. Under the Lateral Movement tactic, the analysis identified Inter-Process Communication: Dynamic Data Exchange (T1559.002) with moderate to high confidence (80%), supported by evidence indicating attack spanned multiple blockchain networks via cross-chain messaging. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating draining approximately $3 million across multiple blockchain networks. Under the Impact tactic, the analysis identified Resource Hijacking (T1496) with high confidence (90%), supported by evidence indicating portalV2 contract’s balance plummeted from $3 million to near zero. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- CrossCurve Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/crosscurvefi/incident/CURCRO1770021757
- CrossCurve CyberSecurity Rating page: https://www.rankiteo.com/company/crosscurvefi
- CrossCurve Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/curcro1770021757-crosscurve-curve-finance-cyber-attack-january-2026/
- CrossCurve CyberSecurity Score History: https://www.rankiteo.com/company/crosscurvefi/history
- CrossCurve CyberSecurity Incident Source: https://thecyberexpress.com/crosscurve-bridge-3m-cyberattack/
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/Images/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf