A $91,000 exploit would barely register among the largest crypto hacks.
For Full Sail, it was enough to end the protocol.
The Sui-based DeFi project announced that it is winding down after an attacker drained approximately $91,000 from three automated vaults in an incident linked to Switchboard oracle infrastructure.
The attacker reportedly exploited a weakness involving who could sign oracle price updates, added a key under their control, caused false prices to be accepted and used those manipulated prices to extract value from affected vaults.
Full Sail said the incident was not caused by the compromise of a Full Sail administrator key.
The protocol has disabled new deposits and liquidity-provider reward claims and plans to move regular pools into withdrawal-only mode after final security checks.
The team says remaining protocol-owned liquidity will be used to reimburse users and that it will cover any shortfall.
The dollar loss is relatively small.
The operational consequence is not.
How the exploit reportedly worked
DeFi protocols often rely on external oracle systems to provide asset prices.
Smart contracts cannot automatically know the real-world market price of an asset.
They need an oracle.
That means the security model is not simply:
Is the smart contract code safe?
It is:
Is every external input the contract trusts safe?
In the Full Sail incident, the attacker reportedly gained the ability to introduce an authorized signing key into live oracle infrastructure.
Once the system accepted that key, manipulated price updates could appear legitimate.
The attacker then used prices roughly 100 times below market in the affected vaults before restoring pricing and withdrawing more value than had been deposited.
The exact technical root cause remains important for the final postmortem, but the economic mechanism is familiar:
corrupt the price input → make the protocol calculate value incorrectly → extract assets.
Why oracle attacks are so dangerous
Oracles are one of DeFi’s most persistent attack surfaces.
Lending protocols use them to determine collateral values.
Vaults use them to rebalance positions.
Stablecoins use them to assess collateral.
Derivatives use them to settle contracts.
If the price feed is wrong, the smart contract can behave exactly as designed and still lose money.
That is the dangerous part.
A perfectly functioning contract can execute a disastrous transaction when the trusted input is false.
This is why DeFi risk has to be evaluated as a full system rather than a single contract.
Why a small exploit can still kill a protocol
The most important lesson from Full Sail is not the size of the hack.
It is the economics of recovery.
A protocol can lose far less than $1 million and still decide that continuing operations no longer makes sense.
Several costs appear after an exploit:
- user reimbursement;
- audits;
- engineering fixes;
- legal work;
- incident response;
- lost liquidity;
- lost user trust;
- higher insurance costs;
- reduced future revenue.
For a small protocol, those costs can exceed the expected value of continuing the business.
Security failures therefore create nonlinear consequences.
A $91,000 direct loss can create a much larger economic loss through shutdown.
The third-party dependency problem
Full Sail’s case also highlights dependency risk.
DeFi protocols rarely operate alone.
They depend on:
- oracle providers;
- bridges;
- RPC infrastructure;
- wallets;
- libraries;
- multisigs;
- front ends;
- blockchains;
- cloud infrastructure.
Each dependency expands the attack surface.
A protocol team may secure its own code while still being exposed to vulnerabilities elsewhere.
The same Switchboard-related incident reportedly affected other applications, including Virtue.
This is why third-party infrastructure must be treated as part of the protocol’s security perimeter.
Why it matters
The DeFi security conversation often focuses on large hacks.
But protocol survivability may be a more useful metric.
Investors should ask:
How large a loss can this protocol survive?
A protocol with large reserves, strong revenue and insurance may survive a major exploit.
A small protocol with weak treasury resources may fail after a much smaller incident.
That introduces a new dimension of DeFi risk:
operational resilience.
Security is not only about preventing an exploit.
It is about whether the project can recover after one occurs.
Oracle risk controls
Protocols can reduce oracle-related risk through multiple layers.
Multiple data sources
Using several independent price sources reduces reliance on one provider.
Price deviation limits
Contracts can reject prices that move too far from recent values.
Time-weighted pricing
TWAP mechanisms can reduce the impact of short-lived manipulation.
Circuit breakers
Vaults can automatically pause when prices behave abnormally.
Role and signer controls
Oracle authorization systems need strict key management and monitoring.
Exposure caps
Protocols can limit how much capital depends on a single oracle or asset.
No control is perfect.
The goal is to make one failure less likely to become a protocol-ending event.
Risks and unresolved questions
The incident still needs a detailed technical postmortem.
It is important to distinguish between Full Sail’s account of the incident and a complete independent root-cause analysis.
Questions remain around:
- the exact Switchboard vulnerability;
- signer authorization;
- affected networks;
- why monitoring did not stop the manipulation earlier;
- whether similar configurations remain active elsewhere.
Users of other protocols relying on the same infrastructure should therefore pay attention even if they were not directly affected.
What to watch next
The most important updates are:
- Full Sail’s final incident report;
- Switchboard’s technical postmortem;
- reimbursement completion;
- other affected protocols;
- oracle configuration changes;
- independent audits;
- whether the affected infrastructure is re-enabled across affected networks;
- new oracle redundancy requirements.
The central lesson is larger than Full Sail.
DeFi protocols are composable.
Their risks are composable too.
A protocol can have secure contracts and still fail because one trusted component outside the core code breaks.
That means the most important security question is no longer:
Is this smart contract audited?
It is:
What does this protocol depend on, and what happens when one of those dependencies fails?
FAQ
How much did Full Sail lose?
Approximately $91,000 was reportedly drained from three automated vaults.
Why is Full Sail shutting down after a relatively small hack?
The direct loss is only one cost. Reimbursement, engineering, audits, lost trust and future operating economics can make continuation uneconomic.
Was a Full Sail admin key compromised?
Full Sail said the incident was not caused by compromise of its own administrator key.
What role did the oracle play?
The attacker reportedly exploited oracle signing infrastructure and caused manipulated prices to be accepted by affected vaults.
Will users be reimbursed?
Full Sail has said remaining protocol-owned liquidity will be used for users and the team intends to cover any shortfall.