Is Symbiotic Safe? Symbiotic Restaking Risks Reviewed
Part of our guide to the EVM

Quick answer. Symbiotic has no single safety answer. Each vault's curator picks its collateral, adapters and applications, and each network's middleware sets penalties. Audits cover specific components and commits. Judge the exact vault, its slashing rules, admin powers and redemption path before you restake.
Video transcript
Symbiotic has no single safety answer. Each vault's curator, adapters and network rules decide your risk.
A vault holds one collateral asset, and its curator sets the strategy. App Adapters tie it to slashing. Liquidity Adapters send it into external strategies.
Authorized roles can add adapters and raise limits, changing what backs your shares. Fixed parameters do not make a vault unchangeable.
Network middleware defines slash conditions. The AppAdapter caps a slash at slashable stake, but does not judge misconduct. Whitelisting is permission, not insurance, and V2 apps do not inherit veto protection.
Audits cover specific components and commits. OpenZeppelin's adapter review left some medium findings acknowledged, not resolved. Bailsec and Statemind Core V2 reviews are listed; we did not review their findings.
Cantina lists a live Symbiotic bug bounty of up to five hundred thousand dollars. That is a ceiling for researchers, not an insurance fund.
In October 2024, Symbiotic's X account was hijacked for fake points phishing, with no verified loss reported. We found no verified core-contract exploit, which is not proof of a clean record.
Before you deposit, check the exact vault by address: its version, curator roles, adapters and limits, middleware penalty rules, and exit path.
Read the full article for the complete checklist. Building an adapter or middleware? Guardian's smart contract audit pairs two independent teams with an invariant suite.
Earlier Design and Core V2
Symbiotic restaking began as shared security: vaults hold collateral that networks can slash when operators break their rules. The feature-complete Ethereum mainnet, with slashing, launched on January 28, 2025.[1, 2]
On July 1, 2026, Symbiotic introduced Core V2. It extends that collateral to back financial obligations such as insurance, credit and tokenized assets.[3]
Symbiotic's curator FAQ still gives guidance for delegation-based V1 vaults and adapter-based V2 vaults.[4]
Our restaking risks guide covers the wider stack, from staking tokens to bridges. Here the focus is one Symbiotic vault.
How Symbiotic Works
A Symbiotic vault holds one collateral asset. Depositors receive transferable ERC-4626 shares, each a proportional claim on that collateral.[5]
A curator runs each vault. It sets the strategy, the supported applications and adapters, the fees and the access controls.
Adapters decide where the collateral works. App Adapters tie it to an application's obligations and its slashing.[6]
Liquidity Adapters deploy it into external strategies, such as lending or tokenized-asset redemption. Each brings its own accounting and withdrawal logic.
The Universal Delegator caps each adapter at the lower of a fixed amount and a share of vault assets. Authorized roles can add or remove adapters, change limits and reorder priority.[7]
Some settings are fixed at deployment, including the collateral asset and the delegator configuration. Fees, deposit limits, whitelists and role permissions can change later.
Symbiotic's repository and V2 deployment guide describe a vault owner able to migrate to versions Symbiotic has whitelisted. Fixed parameters do not make a vault unchangeable.[8, 9]
Yet the public VaultV2 source at commit bcaa6e2 marks migration unsupported and always reverts. No official source we found documents a path from V1 vaults into Core V2.[4, 10]
Symbiotic Protocol Security Audits
Symbiotic keeps a public audit inventory. Checked on November 20, 2026, it lists June 2026 Core V2 reviews by Bailsec and Statemind.[11]
It lists separate reviews of extensions and adapters too. A listing shows a review took place, not what it covered or whether fixes shipped.
Cantina lists a live Symbiotic bug bounty, started February 1, 2026, with a maximum reward of $500,000. That is a ceiling for researchers, not an insurance fund.[12]
Its core scope names VaultV2, the UniversalDelegator, the withdrawal queue and adapters such as AppAdapter and LiquidLaneAdapter. Coverage follows listed addresses, not every third-party vault.[13]
ChainSecurity's 2024 Core report warned that permissionless configurations can be dangerous. Each vault, network and operator, it said, needs its own evaluation.[14]
Its cover is dated August 13, but the final reviewed code arrived August 20.
OpenZeppelin's June 2026 review covered only the Liquid Lane adapter and named supporting contracts. One medium finding, where a single token's oracle failure could freeze the vault, is marked partially resolved.[15]
Another, predictable jumps in asset value that allow timed extraction from passive holders, is acknowledged rather than resolved. Our guide to stepwise jumps in DeFi accounting explains the pattern.
These are statuses at publication, not confirmed vulnerabilities in any live vault.
Read audits as a coverage map. Match each component behind your vault to a reviewed commit, then check what changed since.
| Review | Scope | Dates | Published result |
|---|---|---|---|
| ChainSecurity | Original Core, commit 9e81d85 | Cover Aug 13, 2024; final code Aug 20 | No critical, high or medium; seven low |
| OpenZeppelin | Liquid Lane adapter and supporting contracts | Jun 8 to 17, 2026; published Jul 9 | Seven medium, some acknowledged, not resolved |
| Bailsec | Core V2 | June 2026 | Listed in inventory; findings not reviewed here |
| Statemind | Core V2 | June 2026 | Listed in inventory; findings not reviewed here |
Incidents on Record
The incident in our sources hit Symbiotic's X account, not its contracts. Cointelegraph dated the takeover to October 5, 2024, describing fake points phishing and the team's website warning.[16]
On October 9, ChainCatcher reported that Symbiotic had regained the account and was still investigating.[17]
Neither report gives a verified loss total. Cointelegraph said it did not test the phishing app with a funded wallet.
Our searches found no verified loss from a Symbiotic core-contract exploit. That is a limit of our search, not proof of a clean record.
So use bookmarked domains and Symbiotic's official address list, and read every signature request.[18]
Slashing and Penalty Risk
In the documented V2 integration, the network's middleware defines slash conditions, penalty calculations, access control and any evidence or dispute process.[19]
Only that registered middleware can call the AppAdapter's slash function.[20]
The AppAdapter caps a slash at the available slashable stake, updates its accounting, cuts allocation limits and sends the collateral to its burner.
It does not judge whether the operator misbehaved. A middleware bug or stolen key could impose a penalty the adapter accepts.
Integration parameters name the secured operator and subnetwork, the guarantee duration and the penalty recipient.
Symbiotic must whitelist an AppAdapter before a curator attaches it. Whitelisting grants permission; it does not insure you against a wrong penalty.
V1 vaults chose a slasher: none, an immediate slasher, or a VetoSlasher whose resolvers can block a request. V2 applications do not inherit veto protection.[4, 21]
Only the resolver recorded at the request's capture time can veto, and only before an exclusive deadline. Completed or expired requests cannot be vetoed.
Under the epoch model, a withdrawal requested in epoch k stays slashable until epoch k+1 ends, then becomes claimable. V2 adapters need their own check.[7, 22]
Curator and Liquidity Risk
A curator can change your risk without touching any share-accounting code. Adding an adapter or raising a limit changes what backs your shares.[7]
Symbiotic's risk page tells curators to hold permissions in multisigs or similar setups, and to review allocations and adapter settings regularly.[23]
Liquidity Adapters import the external protocol's risks: liquidity constraints, smart contract risk and issuer-specific risks of tokenized assets.
Redemptions draw on idle assets first. After that, adapters may return capital at once, in part, or only after a settlement period.
For illiquid strategies, the delegator records the outstanding request and retries as liquidity arrives.
Transferable shares do not guarantee a buyer when you need one.[5]
Our vault curator risk guide shows how one listing decision reached lending depositors. Apply the same scrutiny to a Symbiotic curator's adapter choices.
What to Check
Run these checks on the exact vault, by address, before you deposit.
If the collateral is a staking token, its own risks come first. Our liquid staking risks guide covers slashing, discounts and exit queues.
- Networks: test middleware so no slash exceeds slashable stake, every penalty reaches the named recipient, and only valid evidence triggers one.
- Curators: put every role behind a multisig, and document each adapter's limits, exit timing and external dependencies.[23]
- Everyone: alert on adapter additions, limit changes, role grants and migrations the day they land.
| Check | Evidence to ask for | Red flag |
|---|---|---|
| Address and version | Created by Symbiotic's official VaultFactory for its version, V1 or V2 | Address found only in a post or ad |
| Curator roles | Multisig holder behind each role | One key controls the vault |
| Migration power | Who can migrate, to which versions, and whether the hook works | Owner can migrate with no notice |
| Adapters and limits | Current adapters, fixed and percentage caps | Most assets in one external strategy |
| Middleware | Slash conditions, evidence and dispute process | Penalty logic undocumented or unaudited |
| Penalty recipient | Burner or recipient address and its controller | Recipient controlled by the slashing party |
| Veto, V1 vaults | Slasher type, resolvers, veto deadline | Immediate slasher with an unknown network |
| Audit coverage | Report commit matching the deployed code | Audit of another component or commit |
| Exit path | Epoch rules or adapter settlement times | No stated timeline for delayed redemptions |
Building an adapter or middleware on Symbiotic?
Guardian's smart contract audit puts two independent teams on your adapter or middleware, with an invariant suite for slashing, accounting and withdrawal paths that stays with you.
Frequently Asked Questions
What changed in Symbiotic Core V2?
Symbiotic says one deposit can now support several deployment strategies, instead of sitting locked in one isolated use. It also introduced Liquid Lane as a shared settlement layer for tokenized-asset redemptions.[3]
Which firms reviewed Symbiotic's original Core?
Besides ChainSecurity, Symbiotic's inventory lists Statemind, Zellic, OtterSec and Certora in 2024, plus a Cantina contest. Cantina's current core bounty pays $100,000 to $500,000 for critical findings, and excludes issues already described in audits.[11, 13]
Related reading
Sources
- Symbiotic: Symbiotic Arrives on Mainnet
- crypto.news: Symbiotic mainnet goes live on Ethereum
- Symbiotic: Symbiotic Launches Core V2, Bringing Shared Collateral to Insurance, Credit, and Tokenized Assets
- Symbiotic: Vault Operations FAQ
- Symbiotic: Vaults
- Symbiotic: Adapters
- Symbiotic: Universal Delegator
- Symbiotic: Symbiotic Core Smart Contracts
- Symbiotic: Deploy Vault V2
- Symbiotic: VaultV2.sol at commit bcaa6e2fbb4a2e10c416d45f9496865504e23d83
- Symbiotic: Audits and Security Reviews
- Cantina: Symbiotic Bug Bounty: Instructions
- Cantina: Symbiotic Bug Bounty: Core Contracts Scope
- ChainSecurity: Symbiotic Core Smart Contract Security Assessment
- OpenZeppelin: Symbiotic Core v2 Adapters Audit (July 9, 2026)
- Cointelegraph: Symbiotic X hacked, malware is infecting SVG files: Crypto-Sec
- ChainCatcher: Symbiotic review of security incident: Hackers purchased counterfeit domain names and opened corporate accounts, the official Telegram channel has been established
- Symbiotic: Addresses
- Symbiotic: Build an Application
- Symbiotic: AppAdapter.sol at commit bcaa6e2fbb4a2e10c416d45f9496865504e23d83
- Symbiotic: Slashing
- Symbiotic: Epochs and Delays
- Symbiotic: Risks
- Guardian: Smart Contract Audit Services
- Cantina: Symbiotic Bug Bounty: Web Interface Scope
- Cantina: Symbiotic Bug Bounty: Other In-Scope Assets