<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/the-resolv-hack-how-one-compromised-key-printed-23-million-d77t8djef" -->

---
title: The Resolv Hack: How One Compromised Key Printed $23 Million
description: On March 22, 2026, the Resolv DeFi protocol suffered a $23M exploit when an attacker compromised its AWS KMS environment and gained access to the privileged...
canonical: https://daily.dev/posts/the-resolv-hack-how-one-compromised-key-printed-23-million-d77t8djef
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: The Resolv Hack: How One Compromised Key Printed $23 Million | daily.dev
og:description: On March 22, 2026, the Resolv DeFi protocol suffered a $23M exploit when an attacker compromised its AWS KMS environment and gained access to the privileged...
og:url: https://daily.dev/posts/the-resolv-hack-how-one-compromised-key-printed-23-million-d77t8djef
og:image: https://api.daily.dev/og/posts/D77T8dJEf.png
og:image:alt: The Resolv Hack: How One Compromised Key Printed $23 Million
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# The Resolv Hack: How One Compromised Key Printed $23 Million

**[Hacker News](https://daily.dev/sources/hn)** · 7 min read · 0 upvotes · 0 comments

## Summary

On March 22, 2026, the Resolv DeFi protocol suffered a $23M exploit when an attacker compromised its AWS KMS environment and gained access to the privileged SERVICE_ROLE signing key used to authorize USR stablecoin minting. With no on-chain maximum mint cap enforced, the attacker deposited ~$100K–$200K in USDC and used the stolen key to mint 80 million USR tokens (~$25M). The unbacked tokens were converted to wstUSR, swapped through DEX pools into ETH, and extracted before the protocol could respond. USR's peg collapsed 80% before Resolv halted operations. The post-mortem highlights that 18 smart contract audits couldn't prevent an off-chain infrastructure compromise, and argues that real-time on-chain monitoring (specifically Chainalysis Hexagate) with automated pause triggers is now essential for DeFi protocols relying on privileged off-chain signers.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.chainalysis.com/blog/lessons-from-the-resolv-hack/>

## Similar posts on daily.dev

- [How $25 Million Disappeared in 17 Minutes: A Code-Level Autopsy of the Resolv Hack](https://daily.dev/posts/how-25-million-disappeared-in-17-minutes-a-code-level-autopsy-of-the-resolv-hack-ultxks2yk) · Coins Bench · 1 upvotes · 0 comments

---

Tags: [#blockchain](https://daily.dev/tags/blockchain), [#web3](https://daily.dev/tags/web3), [#smart-contracts](https://daily.dev/tags/smart-contracts), [#defi](https://daily.dev/tags/defi)

[View this post on daily.dev](https://daily.dev/posts/the-resolv-hack-how-one-compromised-key-printed-23-million-d77t8djef)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"The Resolv Hack: How One Compromised Key Printed $23 Million","url":"https://daily.dev/posts/the-resolv-hack-how-one-compromised-key-printed-23-million-d77t8djef","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-resolv-hack-how-one-compromised-key-printed-23-million-d77t8djef"},"datePublished":"2026-03-24T06:50:59.923Z","dateModified":"2026-03-24T06:51:33.997Z","description":"On March 22, 2026, the Resolv DeFi protocol suffered a $23M exploit when an attacker compromised its AWS KMS environment and gained access to the privileged...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8fcbe6669db823440fbeb583619d3d8a?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8fcbe6669db823440fbeb583619d3d8a?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Hacker News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Hacker News","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/hn","url":"https://daily.dev/sources/hn"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-resolv-hack-how-one-compromised-key-printed-23-million-d77t8djef","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"blockchain,web3,smart-contracts,defi","timeRequired":"PT7M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Hacker News","item":"https://daily.dev/sources/hn"},{"@type":"ListItem","position":3,"name":"The Resolv Hack: How One Compromised Key Printed $23 Million"}]}
```

