The Security Risks Institutions Inherit When They Move Assets Onchain

How smart contract, dependency, human, integration, and configuration risk have produced real losses — and what a defensible pre-deployment program looks like.

For most institutions bringing assets onchain, the objective is not a target yield or a capital efficiency gain. It is to deploy without incident.

The mandate given to a Head of Digital Assets or a Lead of Asset Digitization is rarely stated as a return target. It is stated as a constraint: do not become the next entry in the exploit ledger. That constraint is rational. A tokenization program that underperforms by fifty basis points is a portfolio conversation. A tokenization program that loses principal to a technical failure is a board conversation, a regulatory conversation, and in most cases the end of the program.

The market data supports the caution. In a survey of over 200 institutional investment and wealth managers published this month, security and custody standards were named the single largest barrier to increasing digital asset allocations — ahead of volatility, liquidity, and market depth. Ninety-two percent said they would increase allocations if security and custody standards improved, and nearly ninety percent said high-profile hacks and DeFi exploits had materially affected their willingness to invest. The January 2026 Coinbase/EY-Parthenon survey of 351 institutional decision-makers found custody security rising sharply year over year as a gating concern, alongside regulatory uncertainty and a stated lack of internal expertise.

Security is not a diligence checkbox in this market. It is the gate.

What institutions are actually deploying

Across our engagements, institutional activity onchain concentrates in four structures. Each one carries a distinct technical risk profile.

Vaults. The ERC-4626 tokenized vault standard, and its asynchronous extension ERC-7540 for positions that cannot settle same-block, are now the default container for onchain asset management. Aggregate TVL across 4626-compliant vaults sits in the range of $25 billion. Morpho Vaults V2 has become the reference architecture for institutional deployments: adapter-based multi-strategy allocation, curator and allocator roles separated from the owner, function-specific timelocks, and optional gate contracts that enforce KYC and whitelisting at the contract level on deposit, withdrawal, and share transfer. Euler v2’s Vault Kit offers a comparable model with per-market risk parameters. In both cases a third-party curator — Gauntlet, Steakhouse, MEV Capital, Re7, kpk, Block Analitica — typically sets collateral eligibility, caps, and oracle selection.

Stablecoins. The GENIUS Act, signed in July 2025, created the permitted payment stablecoin issuer (PPSI) category, with OCC, FDIC, and NCUA implementing rules and FinCEN/OFAC AML and sanctions rulemaking following through 2026. Institutions entering this category do so through white-label issuance platforms (Bridge, Paxos, Coinbase, Brale), programmable issuance protocols such as M0, or a fully custom build with a regulated partner as the regulatory backbone. Each path introduces a different set of privileged mint, burn, and reserve-attestation controls.

Tokenized assets. Tokenized Treasuries and money market funds are the largest live category, with roughly $15 billion in tokenized Treasury products and $34–36 billion in tokenized RWAs overall as of mid-2026. BlackRock’s BUIDL (issued via Securitize, using an ERC-3643 permissioned contract), Franklin Templeton’s BENJI, Ondo’s OUSG and USDY, Superstate’s USTB, Centrifuge’s Janus Henderson JTRSY, and JPMorgan’s JLTXX are the reference implementations. The common design element is a transfer-restricted token: an onchain allowlist maintained by a transfer agent, with the contract rejecting any transfer to an address that has not been onboarded.

Tokenized derivatives. The fastest-moving category and the least mature. Perpetual futures referencing real-world assets have scaled quickly — Hyperliquid’s HIP-3 open interest, Ostium’s RWA-first perpetuals on Arbitrum, and institutional access routed through prime brokers. In parallel, tokenized money market fund shares are being accepted as off-exchange collateral for derivatives margin, and exchange operators including Nasdaq and ICE have moved toward tokenized equity settlement. This category compounds oracle risk, margin risk, and settlement risk in a single instrument.

The benefits institutions cite for moving into these structures are consistent: continuous settlement, collateral mobility, programmable operations, and access to counterparties and product lines that legacy rails do not reach. Those benefits are real. They arrive attached to a risk category most institutional risk functions have never had to price.

A new line on the risk register

Traditional financial risk management is built around economic exposure: market risk, credit risk, counterparty risk, duration, default. The infrastructure on which a position clears, settles, and is recorded has historically been outside the risk model — a DTC, a custodian, and a transfer agent are assumed to function.

Onchain, the infrastructure is the position. Settlement finality, collateral valuation, redemption rights, and administrative control are all expressed in code and in the operational procedures around the keys that govern it. A defect in either can result in total, immediate, and irreversible loss. There is no reversal window and no counterparty to pursue for restitution.

This is not a theoretical concern, and the shape of the risk is now well documented.

Where the losses actually come from

The first half of 2026 was the most-hacked six-month period on record by incident count. Trackers put the total between roughly $970 million and $1.3 billion across 207–344 incidents, depending on methodology — more than double the incident count of H1 2025.

The distribution matters more than the total. Smart contract bugs accounted for the majority of incidents by count but a small minority of dollars lost. By value, roughly three-quarters of H1 2026 losses traced to privileged key misuse and access control failures. Two incidents — Drift Protocol and Kelp DAO — accounted for close to half of all losses in the period, and neither was a smart contract vulnerability.

For an institution, that finding should reframe the entire security budget. An audit is necessary. It is not sufficient, and it does not address the categories that produce the largest losses.

We group the attack surface into five buckets.

1. Smart contract risk

What it looks like in practice: Logic, arithmetic, and access control defects in deployed code, including latent bugs that survive multiple review cycles.

Documented failure — Balancer V2, November 2025 ($128M): A rounding-direction inconsistency in Composable Stable Pool math, present in the codebase since 2021, was compounded through batched swaps to deflate the pool invariant and misprice pool tokens. Drained across eight chains in under two hours. The contracts had been audited repeatedly and formally verified.

2. External dependency risk

What it looks like in practice: Bridges, message-passing layers, oracles, RPC providers, and collateral issued by third parties whose failure propagates into your position.

Documented failure — Kelp DAO, April 2026 ($292M): The rsETH bridge was configured with a single LayerZero verifier. Attackers poisoned internal RPC nodes and DDoS’d external ones, forcing failover to compromised infrastructure, then forged a cross-chain message. Every onchain transaction was valid. The follow-on liquidity flight pulled billions from unrelated protocols and froze Aave depositors who had never touched rsETH.

3. Human risk

What it looks like in practice: Social engineering, blind signing, key compromise, and insider or targeted-employee attack paths.

Documented failure — Drift Protocol, April 2026 ($285M): Attackers posed as a quantitative trading firm, met contributors in person over months, and deposited their own capital to build credibility. They then obtained pre-signed transactions from Security Council members via Solana durable nonces, took admin control, whitelisted a worthless self-priced token as collateral, and withdrew. Twelve minutes. Precedent — Bybit, February 2025 ($1.46B): malicious JavaScript was injected into the Safe{Wallet} signing interface.

4. Integration failures

What it looks like in practice: Composability: your product inherits the failure of an asset, curator, or service you integrated with.

Documented failure — Stream Finance / Elixir, November 2025 (~$285M in mapped debt exposure): A $93M fund-manager loss on xUSD propagated through curated vaults on Morpho, Euler, Silo, and Gearbox. Elixir had lent 65% of deUSD’s backing to Stream; deUSD fell to roughly $0.015 and was wound down. Curators including TelosC (~$124M), MEV Capital, Varlamore, and Re7 absorbed the losses on behalf of their depositors.

5. Misconfigurations

What it looks like in practice: Correct code, wrong parameters: single-signer roles, absent caps, stale or hardcoded oracles, removed timelocks.

Documented failure — Resolv, March 2026 ($80M minted, ~$25M extracted): A privileged service role that authorized mint amounts was a single externally owned account rather than a multisig, and the contract enforced no maximum mint and no oracle bound. A ~$100–200K deposit produced 80M unbacked USR. Related: in the Stream cascade, xUSD markets priced collateral at a hardcoded value, so liquidations never triggered as the real price collapsed. Drift’s timelocks had been removed five days before its exploit.

Three of these five categories are invisible to a standard code audit. All five have produced nine-figure losses inside the last twelve months.

What a defensible program looks like

Regardless of where a team sits in its deployment lifecycle, the sequence is the same.

           
1. Threat model before you build. Map every party that can influence the system: admins, curators, allocators, oracle publishers, transfer agents, liquidators, bridge verifiers, and any address holding a privileged role. For each, document what they can do, what would happen if they were compromised, and how you would detect it. Institutions that skip this step tend to discover the trust map only after an incident.
           
2. Define invariants and their assumptions. Every protocol has properties that must always hold — total shares reconcile to backing, no address can mint beyond a cap, collateral cannot be priced above a published bound. Writing these down is what makes both audit and monitoring meaningful. An alert that does not correspond to a broken invariant is noise.
           
3. Design the governance and key architecture explicitly. Role separation, custody per role, signing thresholds, timelock durations, and a documented procedure for emergency action. The Drift and Resolv incidents were both governance architecture failures expressed through valid transactions.
           
4. Audit the design, not only the code. A code review confirms that a transaction can execute. It does not answer whether it should. Both questions need an owner.
           
5. Build the operational layer before launch, not after. Runbooks for named scenarios — collateral depeg, oracle staleness, liquidation event, unavailable counterparty — with rehearsal. Transaction verification procedures on an independent stack, so that a compromised interface cannot produce a signature. Segregation of duties. An incident response plan with a named decision-maker.
           
6. Launch behind a gate, and scale on evidence. Caps at a small fraction of target size, with a defined schedule for raising them tied to observed system behavior rather than to the calendar.
           
7. Treat assurance as continuous. Dependencies change, curators reallocate, adapters are added, and new vulnerability classes surface — increasingly through frontier AI models applied to codebases that have already passed human review. A point-in-time review of a system that changes weekly provides point-in-time assurance.
         

Why Sherlock

Sherlock has run over 370 audit contests and collaborative engagements, and supports protocols responsible for more than $250 billion in active TVL. That work includes the infrastructure institutions are now building on top of: Morpho Vaults V2, Aave V4, and the XRPL roadmap, among others.

That vantage point is the relevant credential here. The failures above are not exotic; they recur across the same architectural layers. Sherlock’s researchers have reviewed those layers repeatedly across hundreds of implementations, which means the invariants, the trust assumptions, and the configuration errors that produce losses are already mapped rather than being derived from scratch on your engagement.

We work with institutions across the full deployment lifecycle: threat modeling and secure design review, key and governance architecture, code-level audit of custom contracts, detection and response configuration, runbook development and tabletop rehearsal, and ongoing review as the system evolves.

Next step

If you are evaluating a vault, stablecoin, tokenized asset, or tokenized derivative deployment — at any stage from architecture through pre-launch — we will walk your team through the threat model for your specific structure and show you where comparable deployments have failed.

Book a 30-minute technical review →

No preparation required. Bring your architecture, and we will map the attack surface with you.

‍