TL;DR - Most wallet screening checks sanctions, mixer, and stolen-funds exposure on the base asset a wallet holds, not on restaking-contract interactions or liquid restaking tokens like rsETH, so a clean score can still hide real exposure.
Holding a liquid restaking token doesn't put you in a criminal database. It does put you outside almost every plain-language description of what wallet screening actually covers, and the gap got a real-world stress test in April 2026.
The Kelp DAO Hack, in Three Numbers
In April 2026, an attacker drained 116,500 rsETH, worth roughly $292M, from Kelp DAO's cross-chain bridge. That's about 18% of the token's circulating supply, stranded across 20 blockchains in a single exploit. Security researchers traced the attack to a 1-of-1 verifier setup on the LayerZero bridge: one compromised node was enough to approve a fake burn and release real funds on the other side.
The fallout moved fast. Aave paused rsETH-backed lending markets within hours. The Arbitrum Security Council froze roughly $71M in funds linked to the exploit, moving them into an intermediary wallet that needs a governance vote to unlock. Investigators pointed to North Korea's Lazarus Group as the likely operator, the same attribution pattern behind several of the largest crypto thefts on record.
The April 2026 Kelp DAO restaking-bridge exploit, attributed to North Korea's Lazarus Group, at a glance.
What Is Restaking, and Why Does Kelp DAO's rsETH Matter?
Restaking lets ETH already staked to secure Ethereum get pledged a second time, through EigenLayer, to secure other services at the same time. Kelp DAO is one of the largest liquid restaking protocols built on top of EigenLayer. Deposit ETH, and Kelp hands back rsETH: a tradeable token that represents your restaked position and still moves freely across DeFi.
That liquidity is the entire selling point. It's also why a restaked position runs through six or seven separate contract systems in sequence: the Ethereum staking contract, EigenLayer's core contracts, the individual AVS you're securing, Kelp's own issuer contract, the rsETH token, and often a lending market on top if you're looping for extra yield. Each layer is an independent failure point. The Kelp hack hit one of them, the cross-chain bridge, not the restaking logic itself.
EigenLayer's own slashing rules went live in 2025 and are now enforceable on mainnet, so a fault in one AVS can dock actual restaked balances, not just theoretical ones. That's a separate risk from the Kelp bridge exploit, and it's worth knowing both exist before you assume "restaking" means one thing with one risk profile.
Why Didn't Wallet Screening Catch the Exposure?
Standard wallet screening, this one included, is built around addresses and known labels: sanctions lists, mixer contact, scam clusters, stolen-funds tags. That model works well for a plain ETH or USDC transfer. It works less well the moment the asset in the wallet is an LRT, because the receipt shows up as an ordinary ERC-20 transfer, and nothing about that transfer says whether the tokens came from a clean deposit or from bridge funds an attacker just laundered through a swap.
This is the same gap covered in the ERC-4337 blind spot and the EIP-7702 delegation blind spot: the account-abstraction and restaking stacks both hide the thing that actually matters a layer or two below what a bytecode or balance check reads. A wallet holding rsETH looks identical to a wallet holding any other liquid staking derivative, right up until a label database catches up with the specific contract addresses tied to an exploit.
The Structural Blind Spot Behind LRTs
Plastron's own corpus carries 121 addresses tagged for hack or exploit exposure, out of roughly 3,901 labeled addresses total. Every one of those got added after the fact, once researchers traced stolen funds to a specific address. A brand-new bridge exploit doesn't arrive pre-labeled. There's a window, sometimes days, where the exact addresses tied to a hack like Kelp DAO's simply aren't in any screening database yet, no matter how good the tool is.
A wallet that received rsETH minted before the hack, then interacted with the compromised bridge contract afterward, sits in exactly that window. The transaction history looks ordinary. The risk isn't. One bridge exploit is worse for a screening tool than ten hops through a known mixer, because a mixer at least gets flagged on contact.
The Kelp DAO case makes the timing problem concrete. An open-source AI monitoring tool reportedly flagged the vulnerable verifier configuration twelve days before the exploit happened, and nobody acted on it. If a warning that specific can sit unread for twelve days, a generic address-screening database catching up on the resulting theft in hours isn't realistic.
A restaked position runs through five or six contract layers. Standard wallet screening reads the token balance at the top; the exploit sat two layers down.
What Should You Check Before Holding or Moving an LRT?
Treat any LRT balance the same way you'd treat a large stablecoin balance from an unfamiliar source: worth five extra minutes before you move it.
Re-screen the wallet after any restaking deposit, withdrawal, or bridge interaction, not from a score you ran last month.
Check the protocol's own incident page directly for the exact contract addresses involved in a hack; label databases catch up days or weeks later, not instantly.
Treat funds that moved through a frozen or paused bridge, like Kelp's, as stolen-funds exposure until proven otherwise, the same way you would for crypto received from any hacked protocol.
For six figures or more sitting in an LRT, confirm the AVS and issuer contracts through the project's official documentation before assuming a clean wallet score covers the whole stack.
Anyone can check a contract address against a block explorer for free. Screen the wallet with Plastron instead, and the same pass covers sanctions, mixer, and stolen-funds exposure across Ethereum and six other chains, not just whichever piece of the restaking stack happens to be labeled yet.
FAQ
Does holding rsETH or another LRT automatically flag a wallet as high risk?
No. An LRT balance by itself isn't a risk signal. The risk depends on whether the specific contracts or bridge routes behind that balance have been tied to a hack, sanction, or scam, which a screening check can only tell you once that link has already been labeled.
Was Kelp DAO itself hacked, or just its bridge?
The bridge. The attacker exploited a single-verifier weakness in Kelp's cross-chain LayerZero setup, not the restaking or slashing logic EigenLayer itself runs. Kelp's core contracts stayed intact throughout the incident.
How long does it take for hack-related addresses to show up in a screening database?
It varies. Well-tracked cases can get flagged within days once researchers publish the attacker's addresses; smaller or slower-moving exploits can take weeks. That lag is exactly the window this blind spot lives in.
Does freezing funds, like Arbitrum did with the $71M linked to this hack, mean my wallet is safe?
Not on its own. A freeze protects the specific funds a security council can identify and reach. It doesn't retroactively clean every wallet that touched the bridge before the freeze happened, so screening the wallet directly still matters.
Disclaimer: This article is for educational and informational purposes only and is not legal, financial, tax, or compliance advice. Crypto carries risk; you act on this information at your own risk. Always do your own research and consult a qualified professional before making decisions. Views are the author's own and do not constitute financial, legal, or investment advice.
About Plastron
Plastron is a free, non-custodial wallet screening tool. It checks Ethereum and six EVM chains for AML and KYT risk — sanctions exposure, mixer contact, and stolen-funds proximity — and returns a risk report in seconds. It reads public on-chain data only: it never takes custody of funds and never asks for private keys.