The $91,000 drain
The attacker hit three vaults, pulling out about $91,000 in total. Full Sail hasn't said how the exploit worked, but it has tied the incident to Switchboard, which supplies price data to DeFi applications. Oracle providers are a critical piece of DeFi infrastructure. They bring off-chain information, like asset prices, onto the blockchain. If that data is wrong or can be manipulated, it can open the door to attacks.
The Switchboard connection
Switchboard is an oracle service that feeds data into blockchain protocols. Full Sail said the incident was linked to Switchboard, though it didn't specify whether the problem was in Switchboard's code or in how Full Sail used the data. The protocol didn't offer more details.
Shutdown and what's next
Full Sail is closing down. The protocol hasn't said when the shutdown will be complete or how users should move their funds. That leaves users waiting for instructions. The incident is a reminder that third-party dependencies can be a weak link in DeFi, but for now, the immediate question is what happens to the money still in Full Sail's vaults.
That's about 200 words. We need 500-800. We can expand by adding more context about Sui, but we don't have facts. We can say "Sui is a layer-1 blockchain" - that's general knowledge. We can say "Full Sail is one of the protocols built on Sui" - that's inference. We can say "The shutdown is a blow to the Sui DeFi ecosystem" - that's editorial. We can add a paragraph about the broader implications of oracle security, but we must not attribute to experts. We can say "Oracle vulnerabilities have been a recurring theme in DeFi hacks" - but that's a general statement, but we don't have a specific example. We can say "The reliance on oracles is a known risk" - that's fine. We can also mention that the attacker removed funds from three vaults, and that the protocol is shutting down as a result. We can say "The decision to shut down comes after the incident" - that's a logical connection. We can also say "Full Sail has not said whether it will reimburse affected users" - that's a negative claim, but we don't know. We can say "It's unclear if users will be compensated" - that's a statement of uncertainty. We can write a longer piece by discussing the mechanics of oracle attacks, but we must not invent specifics. We can say "In a typical oracle attack, an attacker manipulates the price feed to trigger trades at favorable rates"
