CSIDB logo
Incident

Resolv

Incident posture

Attack window
Mar 2026
Location
-
Status
Unknown
CIA posture
Available to members
Updated
2026-08-17 05:41

Linked entities

Victim
Resolv
Threat actors
0 actors
Sources
1 source

Timeline

Occurred
Mar 2026
Discovered
Pending
Disclosed
Pending
Resolved
Pending

Summary

An attack on the yield protocol Resolv resulted in approximately $25 million in losses. The incident highlights how AI‑driven tools are reducing the cost and effort needed to discover and exploit vulnerabilities in crypto protocols. Alongside other recent exploits, such as the Drift protocol breach, the incident contributed to over $1.4 billion in crypto losses reported over the past year.

Motives

Detailed motive labels are available to members.

0 motives

TTPs

Detailed technique labels are available to members.

0 techniques

Description

Approximately one week before April 5, 2026, the yield protocol Resolv suffered an attack resulting in approximately $25 million in losses. This incident occurred roughly one week before the exploitation of the Solana-based Drift protocol, which was reported in early April 2026 and led to $285 million in losses. The article reporting these events was published on April 5, 2026, by CoinDesk. The source cites data from DefiLlama indicating over $1.4 billion in assets were stolen or lost in crypto attacks over the past year. The Resolv attack is described as an attack on a yield protocol.

The article notes that the Resolv exploit contributed to the broader trend of increasing crypto heists, with AI-driven tools lowering the cost and difficulty of finding and exploiting vulnerabilities, as warned by Ledger CTO Charles Guillemet. The financial impact of the Resolv incident was a direct loss of $25 million worth of digital assets. No further details about attacker identity, method, detection, containment, or remediation are provided in the source material. The article does not specify any immediate response actions taken by the Resolv team following the exploit. The narrative ends here.

Sources

Sources available to members: 1 source.

CSIDB