The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →On April 18, 2026, an attacker caused KelpDAO’s LayerZero-powered rsETH bridge to release about 116,500 rsETH, worth roughly $290 million to $292 million at the time. LayerZero, Mandiant, CrowdStrike and independent security researchers attributed the operation to the DPRK-linked TraderTraitor group, also known as UNC4899. That attribution remains an incident-response assessment, not a publicly documented court finding.
The attack was not simply a case of “North Korea hacking KelpDAO.” It involved allegedly compromised RPC infrastructure, a forged cross-chain message and a 1-of-1 verifier configuration. The unbacked rsETH was then used as collateral on Aave, creating secondary exposure for the lending protocol and its users.
As an Amazon Associate I earn from qualifying purchases.
The short version
KelpDAO is a liquid-restaking protocol whose rsETH token represents claims on underlying ETH-related assets and restaking rewards. Its bridge route from Unichain to Ethereum was configured so that one LayerZero decentralized verifier network (DVN) attestation was sufficient to approve a cross-chain message.
Recommended Free Tools
According to LayerZero’s later incident report, attackers first socially engineered a LayerZero developer and obtained session keys. They then compromised and poisoned RPC infrastructure used by the DVN. The manipulated infrastructure allegedly supplied a plausible-looking response for a forged message. Because the route required only one verifier, the destination-side adapter released rsETH without a corresponding source-side burn.
#1 Best Overall
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Enjoy Bluetooth connectivity, iOS access, and hours of battery use with this mobile-first, secure backup signer. Freedom you can depend on.
- Genuine Check: confirm your signer is authentic during setup with the Ledger Wallet app.
- Protect your signer: keep it in mint condition at all times with a bespoke Pod or Case to avoid scratches and everyday wear and tear.
The attacker transferred the resulting rsETH into DeFi markets. Aave’s incident report says approximately 89,567 rsETH was deposited there and used to borrow WETH and, in some positions, wstETH. Aave froze affected rsETH and wrsETH markets, while the broader ecosystem debated recovery and responsibility.
What are KelpDAO and rsETH?
KelpDAO is a liquid-restaking protocol. Users deposit eligible ETH-related assets and receive rsETH, a liquid token intended to represent the value of those deposits plus associated staking or restaking rewards.
rsETH is not ordinary ETH. Its safety depends on the quality of its backing, the protocol’s issuance and redemption controls, bridge design, and the assumptions made by DeFi applications that accept it. A bridge that releases an unbacked representation can create a token that looks legitimate on-chain but no longer corresponds to assets held on the source side.
In this incident, the relevant bridge route moved rsETH between Unichain and Ethereum using LayerZero infrastructure. The core economic rule should have been simple: assets released on the destination chain must correspond to assets locked or burned on the source chain.
What happened on April 18, 2026?
- March 6: LayerZero’s later report says the intrusion began when an attacker socially engineered a LayerZero developer and harvested session keys.
- 17:35 UTC on April 18: The attacker exploited the Kelp rsETH route from Unichain to Ethereum.
- Ethereum block 24,908,285: Aave’s report identifies the block containing the forged inbound packet that released 116,500 rsETH without a matching source-side burn.
- About 18:52 UTC: Aave’s Guardian began freezing rsETH and wrsETH markets.
- About 19:00 UTC: LayerZero said affected RPC nodes had been identified and later deprecated or replaced.
- April 19–20: LayerZero publicly attributed the attack to likely DPRK-linked actors and criticized KelpDAO’s single-DVN configuration. KelpDAO disputed that account.
- May 20: LayerZero published a more detailed report describing the alleged social-engineering, RPC compromise and post-incident configuration changes.
LayerZero valued the released tokens at approximately $290 million to $292 million, depending on the valuation time and source.
How the exploit worked
1. The attacker allegedly compromised verification infrastructure
An RPC, or remote procedure call endpoint, is infrastructure that answers queries about blockchain state. Wallets, applications and verification systems use RPC services to retrieve information such as transaction data, balances and block contents.
LayerZero’s account says the attacker used stolen session keys to enter its RPC cloud environment and poison internal nodes. The altered software allegedly returned normal-looking information to monitoring systems while supplying manipulated responses to the DVN. LayerZero also said the attacker conducted a denial-of-service attack against an external RPC provider, forcing the DVN to rely on two compromised internal nodes.
Free tools Windows power users keep installed
One-click scans. No signup required.
In that account, the attacker did not merely submit an invalid transaction and hope a contract accepted it. The alleged attack manipulated part of the information pipeline used to determine whether a cross-chain message was authentic.
2. A forged message passed a 1-of-1 check
LayerZero’s DVN system is intended to help verify that a message was sent from the correct source chain and application. KelpDAO’s route was configured as 1-of-1: one required DVN attestation was enough for the message to proceed, and LayerZero Labs was the sole verifier.
The destination-side adapter therefore accepted what appeared to be a valid attestation and released approximately 116,500 rsETH. Aave’s analysis says there was no corresponding source-side burn.
Rank #2
- Proven security at scale: Over 9 years and millions of cards issued with no known remote hacks, while military‑grade EAL6+ security keeps your private keys locked inside the chip. Your cryptocurrencies stay strongly protected from online attackers.
- Tap once to manage your entire crypto wallet across 90 blockchains - no USB cables or Bluetooth, no batteries, no setup. Access 14,100+ coins & tokens, DeFi, NFTs, and staking instantly from your phone
- Smart backup: Use your second Tangem Wallet as your Backup keys with end‑to‑end encryption; no more papers, pictures. If one card is lost, the remaining can still restore full access, with an optional seed phrase available for advanced users.
- Engineered to last up to 25 years: Waterproof (IP69K), shockproof and tested for extreme temperatures from −25°C to 50°C. A durable cold wallet with long‑term protection and independently audited security.
- Trusted by 6 million users worldwide - buy, sell, swap, stake, and spend cryptocurrency directly. The secure offline storage wallet designed for how people actually use crypto wallets
This created a single point of trust and failure. The route’s contracts may have followed their programmed rules, but those rules accepted a message whose economic claim was false.
Was this a smart-contract bug?
Public postmortems have framed the primary failure as compromised verification infrastructure combined with an unsafe single-verifier configuration, rather than a newly disclosed arithmetic or coding flaw in Aave’s lending contracts.
OpenZeppelin described the incident as an example of a system failing because of assumptions and trust boundaries even when no obvious underlying code bug was identified. That does not mean “there was no bug anywhere.” It means the central weakness described in the available reports was the interaction between operational security, message verification and configuration.
A useful distinction is this: the destination contract appears to have accepted a message that satisfied its configured verification requirement. The problem was that the verification requirement was not sufficiently independent or defensive to establish that the message represented a real source-side event.
OpenZeppelin’s analysis discusses why a protocol can behave as designed while the design itself creates unacceptable risk.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Why LayerZero blamed KelpDAO
LayerZero said KelpDAO’s rsETH route used LayerZero Labs as the sole required verifier, despite best-practice guidance favoring multiple independent DVNs. In LayerZero’s view, a second independent attestation could have rejected the forged message or at least made the attack substantially harder.
LayerZero also said:
- the attack was isolated to KelpDAO’s rsETH configuration;
- other LayerZero applications and cross-chain assets did not suffer the same direct exploit; and
- it had previously recommended DVN diversification.
That argument identifies the 1-of-1 setting as an important enabling condition. It does not, by itself, settle responsibility for the alleged compromise of the infrastructure supporting LayerZero’s verifier.
LayerZero’s initial and later accounts are available in its incident statement and incident report.
Why KelpDAO blamed LayerZero
KelpDAO disputed LayerZero’s effort to place primary responsibility on Kelp’s configuration. As reported by CoinDesk, Kelp argued that the single-verifier arrangement relied on LayerZero infrastructure and that LayerZero’s defaults or prior confirmations supported the configuration.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchKelp’s position was that it was misleading to describe the incident solely as an integrator’s failure when the compromised infrastructure belonged to or supported the DVN used to verify the route.
Rank #3
- UNPARALLELED SECURITY: Protect your assets with Trezor Safe 5's NDA-free EAL 6+ Secure Element, offering robust defense and complete transparency.
- EFFORTLESS NAVIGATION: Experience seamless crypto management with the vibrant color touchscreen, designed for intuitive and user-friendly interactions.
- ENHANCED USER EXPERIENCE: Enjoy tactile confirmation with Trezor Touch Haptic Engine, making each interaction precise and engaging.
- SUPPORTS 1000s OF COINS & TOKENS: Securely handle thousands of assets, including Bitcoin, Ethereum, and more, all in one wallet.
- EASY ASSET MANAGEMENT: Monitor and transact seamlessly with Trezor Suite, our user-friendly desktop and mobile app
The available accounts establish the technical sequence more clearly than they establish legal or commercial responsibility. The blame dispute remains unresolved, and LayerZero’s statements should be understood as the account of a party directly involved in the incident.
How Aave became exposed
The stolen asset’s use on Aave transformed a bridge incident into a lending-market crisis.
- The attacker obtained rsETH that was not properly backed by a corresponding source-side asset movement.
- Approximately 89,567 rsETH was deposited on Aave, according to Aave’s April 20 incident report.
- The attacker used rsETH as collateral to borrow WETH and, in some positions, wstETH.
- Once the backing of rsETH was questioned, those loans could create bad debt because the collateral might not be worth what Aave’s risk model assumed.
- Aave froze rsETH and wrsETH markets to prevent additional borrowing and deposits.
Aave reported active rsETH-backed loans across Ethereum and Arbitrum, with individual health factors around 1.01 to 1.03 at the time of its report. A health factor close to 1 means a position has little room for the collateral’s value to fall before liquidation conditions are reached.
Aave explicitly said the incident was scoped to rsETH and did not originate from a vulnerability in Aave’s core protocol. The lending protocol accepted a listed collateral asset whose backing had been undermined elsewhere.
See Aave’s technical incident report and its initial incident response.
How large was the wider DeFi impact?
The headline theft amount, the amount deposited on Aave, the amount borrowed, temporary withdrawals, and eventual bad debt are different figures. They should not be treated as interchangeable.
SecurityWeek reported sharp market reactions, including withdrawals and utilization changes. Aave’s official reports document the affected markets, freezes and exposure. Later governance discussions considered DAO participation in restoring rsETH backing through a broader “DeFi United” recovery effort.
Those discussions should not be described as completed compensation unless an official vote and implementation establish that users were made whole. Likewise, temporary declines in total value locked or large withdrawals do not automatically prove equivalent permanent losses.
Aave governance later published an rsETH incident funding update covering recovery proposals.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What changed afterward?
LayerZero said it rebuilt the operational infrastructure associated with the compromise and changed its participation policy. Its DVN would no longer sign as the sole required attestor on a channel in which it participates.
Rank #4
- Dual-chip architecture for maximum protection: The next-gen, fully auditable TROPIC01 chip works alongside a certified EAL6+ Secure Element—completely NDA-free—to deliver radically transparent, industry-leading defense against physical attacks.
- Quantum-ready security: Get protection against future threats with the first-ever hardware wallet designed with quantum-ready architecture.
- See every detail with confidence: Our largest high-resolution color touchscreen makes it easy to navigate your assets, review transactions and manage your coins with clarity.
- Wireless freedom with encrypted Bluetooth control: Manage, buy, swap and stake securely using Trezor Suite on desktop or mobile. Qi2-compatible wireless charging keeps your Trezor powered up. No cables required—security meets convenience.
- Works seamlessly with Android, iOS and desktop: Connect wirelessly or via USB-C to your phone or computer. Manage your crypto anywhere with our companion Trezor Suite app.
This did not mean that LayerZero changed every rule in its underlying on-chain protocol. Rather, LayerZero Labs changed the configurations its own DVN would support, moving from broad integrator configuration freedom toward a baseline security requirement.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →The change addresses verifier concentration, but it cannot eliminate every cross-chain risk. Multiple verifiers are useful only when they are genuinely independent. Five verifiers using the same cloud provider, RPC source, codebase or administrative credentials may still represent one correlated failure domain.
The broader security lessons
Use independent verification
Requiring multiple DVNs can reduce the chance that one compromised verifier authorizes a forged message. The trade-offs include higher fees, greater complexity, added latency and possible liveness problems when one verifier is unavailable.
Protect the backing invariant
Bridge contracts and monitoring systems should independently check that released or minted supply corresponds to locked or burned source-side assets. A message that is cryptographically well-formed is not necessarily economically true.
Add route-level limits
Per-asset and per-route withdrawal caps, rate limits, velocity monitoring and delayed execution for unusually large transfers can reduce the damage from a single forged approval.
Separate infrastructure and monitoring
Verification nodes, cloud environments and RPC providers should not all share one operational trust boundary. Monitoring is less useful when it queries the same potentially compromised data path as the verifier it is supposed to supervise.
Limit collateral contagion
Newly bridged or derivative assets may warrant conservative collateral parameters, isolation-mode markets or automatic collateral disabling when backing cannot be independently verified. Freezing a market prevents new exposure but does not automatically remove existing bad debt.
What remains unresolved?
The incident reports leave several questions open: the complete initial intrusion path, the final legal and law-enforcement attribution, the allocation of recovery costs, and whether every affected user will ultimately be made whole.
The narrow conclusion is clearer. This was a cross-chain verification and backing-invariant failure involving allegedly compromised infrastructure and a 1-of-1 verifier configuration. It was not simply “a bridge minted money,” and it was not evidence that all LayerZero applications or all Aave markets were compromised.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
