The decentralized finance ecosystem on the Sui network has faced another painful lesson: the Full Sail project has announced its closure after the exploitation of a vulnerability related to the Switchboard oracle. As a result of the attack, the malicious actor managed to withdraw approximately $91,000 from three protocol vaults, which proved to be a fatal blow to the platform's operational resilience.
According to my analysis, the incident is systemic in nature, affecting not only financial losses but also trust in DeFi infrastructure components. The project's administration has already suspended the acceptance of new deposits and the accrual of rewards, which is a standard but belated response measure. The key question here is why the oracle protection mechanism did not activate at early stages, given that such attacks on price feeds are becoming increasingly sophisticated.
The Full Sail team has stated its intention to use its own liquidity to cover user losses. In the event of insufficient funds, additional financing is planned to ensure priority restoration of depositors' funds. This approach demonstrates a responsible attitude toward the community, but it does not negate the fundamental problem: a protocol built on external dependencies remains vulnerable to manipulation if multi-layered data verification is not implemented.
For the market, this is a signal of the need to revise security standards when integrating oracles. Projects should implement redundant data sources and emergency braking mechanisms rather than relying on single points of failure. The complete closure of Full Sail will likely become a precedent that will force other teams on the Sui network to reconsider their architectural decisions.
My expert assessment: the incident highlights that even attacks of small scale can lead to the collapse of projects if their business model does not provide sufficient liquidity buffers. In the long term, the market will benefit from stricter auditing and standardization of oracle solutions, but for now, users should exercise increased caution when interacting with young protocols.