CSIDB logo
Incident

Cryptocurrency Organization

Incident posture

Attack window
Mar 2023
Location
United States of America
Status
Historical
CIA posture
Available to members
Updated
2025-11-14 00:00

Linked entities

Victim
Cryptocurrency Organization
Threat actors
0 actors
Sources
1 source

Timeline

Occurred
Mar 2023
Discovered
Pending
Disclosed
Pending
Resolved
Pending

Summary

An attack targeted Euler protocol, prompting immediate actions to halt the exploit by disabling the vulnerable EToken module, which blocked further deposits and malicious transactions. The organization engaged blockchain analysis firms and the broader ETH security community for investigation and fund recovery efforts, while also notifying law enforcement agencies in the US and UK, and initiating contact with the attackers to explore potential resolutions.

Motives

Detailed motive labels are available to members.

1 motive

TTPs

Detailed technique labels are available to members.

1 technique

Description

On March 13, 2023, Euler Finance, a cryptocurrency lending protocol, experienced a security incident involving unauthorized access to its systems. The attack exploited vulnerabilities in the protocol’s EToken module, specifically targeting a donation function that allowed malicious actors to manipulate transactions. Upon detecting the breach, Euler Finance’s team immediately disabled the compromised EToken module, effectively halting further deposits and blocking the vulnerable function to prevent additional fund losses. This containment action was prioritized to stop the direct attack vector and stabilize the protocol’s operations. Concurrently, the organization initiated contact with blockchain analytics firms TRM Labs and Chainalysis, as well as members of the broader Ethereum security community, to assist in investigating the attack’s mechanics and tracing the movement of stolen funds.

Euler Finance formally notified law enforcement agencies in the United States and the United Kingdom, sharing relevant incident details to support potential legal actions. The organization also attempted to establish communication with the attackers, seeking to negotiate or gather intelligence regarding fund recovery options. The primary operational impact centered on the disruption to user deposits and the protocol’s lending functions due to the forced disabling of core modules. Recovery efforts focused exclusively on tracing stolen assets and exploring avenues for restitution, though the incident’s full financial scope and user impact were not publicly quantified in the immediate response phase. No additional technical specifics regarding the attack vector or the attackers’ identity were disclosed at this stage.

Sources

Sources available to members: 1 source.

CSIDB