DeFi protocol Full Sail, built on the Sui blockchain, has decided to shut down completely following a security incident involving oracle provider Switchboard that resulted in user losses. The protocol immediately disabled new deposits and LP reward claims, while regular pools were moved into withdrawal-only mode after final security checks.
Key fact: The attacker drained around $91,000 from three Full Sail automated vaults. The protocol is using all remaining protocol-owned liquidity to compensate users, and the team has committed to covering any shortfall so community depositors are repaid first.
The incident began unfolding on Saturday, when Full Sail first disclosed the issue, confirmed that funds had been lost, and paused deposits and withdrawals while an investigation was carried out. By Tuesday, the protocol announced that it would cease operations entirely and published a more detailed explanation of the situation on X.
| Day | Event | Action |
|---|---|---|
| Saturday | Abnormal activity detected in automated vaults | Deposits and withdrawals paused, investigation launched |
| Saturday | Switchboard confirms potential compromise | Network operations suspended on Aptos, Sui, IOTA, and Movement |
| Sunday-Monday | Damage assessment and investigation | $91,000 in losses confirmed across three vaults |
| Tuesday | Full shutdown announced | New deposits and LP claims disabled, pools moved to withdrawal-only mode |
Switchboard, an oracle provider operating across multiple blockchain ecosystems, said it was investigating a potential compromise affecting its Move-based deployments. The company temporarily suspended operations across four networks:
Critical impact: A compromise affecting shared oracle infrastructure can expose multiple protocols at once, turning what might otherwise be an isolated exploit into a broader ecosystem-level risk.
The incident affected more than Full Sail. Other protocols relying on Switchboard infrastructure were also exposed, with Virtue, a stablecoin lending protocol on IOTA, reportedly suffering significantly larger losses.
| Protocol | Blockchain | Losses | Additional Impact |
|---|---|---|---|
| Full Sail | Sui | $91,000 | Complete shutdown |
| Virtue | IOTA | $455,000 | Impairment of VUSD collateral |
| Total | - | $546,000 | Broader concerns over oracle infrastructure risk |
The situation surrounding VUSD is particularly sensitive because losses at Virtue may affect the assets backing the stablecoin. If collateral is impaired, the protocol may face pressure on redemption confidence and market liquidity.
Oracles are critical components in decentralized finance because smart contracts cannot independently access external market data. They rely on oracle systems to provide prices and other information needed for lending, trading, liquidation, and automated strategies.
If an oracle feed or the infrastructure responsible for publishing it is compromised, protocols relying on that information may begin making incorrect decisions automatically.
Critical vulnerability: Automated vaults are especially sensitive to bad oracle data because their strategies can execute immediately when predefined price conditions are met.
The affected deployments were built for Move-based blockchains such as Sui and Aptos. Move uses a resource-oriented programming model designed around digital assets, but that does not make applications automatically immune to security failures.
The ecosystem is also younger than Ethereum's Solidity environment, which means there is generally less battle-tested infrastructure, fewer years of production experience, and a smaller pool of specialists familiar with complex Move-based DeFi systems.
Full Sail's response focused on limiting further losses and prioritizing the repayment of depositors.
Protocol-owned liquidity can give a DeFi project more flexibility during a crisis because those assets are controlled by the protocol rather than individual liquidity providers.
Important point: Full Sail's decision to use protocol-owned liquidity and team funds for compensation may reduce losses for depositors, but it also confirms that the incident was severe enough to make continued operation impractical.
The Switchboard incident highlights a recurring problem in DeFi: protocols that appear independent can still depend on the same infrastructure providers.
Protocols can reduce this type of exposure by designing systems that do not blindly trust a single source of external data.
The incident is likely to increase attention on oracle resilience rather than simply oracle accuracy. A price feed can be accurate most of the time and still represent a serious risk if the infrastructure publishing it can be compromised.
Future systems may increasingly combine multiple providers, cryptographic verification, anomaly detection, fallback mechanisms, and stricter access controls.
Industry trend: Oracle security is gradually shifting from “is the price accurate?” toward the broader question of whether the entire data-delivery pipeline can remain trustworthy under attack.
The Full Sail incident provides several practical lessons for DeFi developers and protocol operators.
The direct losses in this incident are relatively modest compared with some of the largest DeFi exploits, but the economic impact extends beyond the stolen funds.
Full Sail is shutting down entirely, which means the exploit destroyed the value of the protocol as an operating business. Users also experienced temporary restrictions on access to their funds, while Switchboard faces reputational damage and increased scrutiny from projects relying on its infrastructure.
Broader consequences can include lower TVL, reduced activity, higher security spending, and more cautious adoption of newer infrastructure providers.
Many historical DeFi exploits involved attackers manipulating thin markets so that an oracle reported a distorted price. The Switchboard case is potentially more serious from an infrastructure perspective because the reported issue involved the oracle implementation itself rather than simply market manipulation around a valid data source.
That distinction matters. A manipulated market can sometimes be mitigated with stronger pricing methodology, longer time-weighted averages, or deeper liquidity requirements. A compromised oracle infrastructure layer requires a different response focused on software security, key management, deployment controls, and redundancy.
Security lesson: DeFi protocols must defend against both bad market data and compromised infrastructure. Those are different threat models and require different protections.
Full Sail's shutdown after the Switchboard oracle incident demonstrates how deeply DeFi protocols depend on infrastructure they do not fully control. Around $91,000 was lost from Full Sail vaults, while Virtue on IOTA reportedly suffered another $455,000 in losses.
For Full Sail, the incident became a terminal event. The team chose to stop operations, use remaining protocol-owned liquidity for compensation, and cover any shortfall so depositors can be repaid first.
The broader lesson is more significant than the dollar amount involved. Decentralized applications can still contain concentrated infrastructure dependencies, and a failure at one oracle provider can affect several protocols and networks at the same time.
Strategic takeaway: DeFi security is no longer just about auditing smart contracts. Projects also need to understand, diversify, monitor, and protect every external infrastructure dependency that can influence those contracts.
As DeFi systems become more interconnected, resilient architecture will increasingly depend on multiple independent data sources, circuit breakers, fallback infrastructure, and clear incident-response procedures. The safest protocol is not necessarily the one with the fewest dependencies, but the one designed to survive when one of those dependencies fails.
