TruthFoundry News
Better tools. Better news.
Saturday, October 24, 2026 · UTC
Crypto

Switchboard Oracle Compromise Triggers Liquidations and Frozen Vaults

A compromise in Switchboard's Move implementations caused losses, liquidations, and access pauses across DeFi protocols on Aptos, Sui, IOTA, and Movement.

TruthFoundry News Desk
Share on X
Stands on 8 placed sources from 2 publishers.
As of 2026-09-03 04:46 UTC. Market figures are as the cited sources reported them at that time and may have moved since. This is news, not investment advice.
Switchboard, an oracle provider, said contributors halted its deployments on Aptos, Sui, IOTA, and Movement after reports of a potential compromise in its Move-language implementations. [1] Full Sail, a decentralized exchange on the Sui network, announced on September 1, 2026, that it is winding down operations after an attacker drained roughly $91,000 from three of its vaults on August 29. [2] At least three applications reported losses, freezes, or precautionary access restrictions following the Switchboard incident. [3] Full Sail confirmed that its vaults lost funds and said deposits and withdrawals would remain paused until oracle integrity was restored and verified. [4] Virtue, an IOTA credit protocol, said an attacker gained control of the signing keys used by all 14 oracles on Switchboard's IOTA mainnet queue and pushed IOTA's reported price to $10 million. [5] Full Sail paused deposits and withdrawals after confirming the incident on August 29 and committed to returning funds to affected users while absorbing the shortfall. [6] Full Sail stated that the attack was not an admin key compromise but involved direct liquidity pool positions, allowing the attacker to deposit funds and withdraw more than the deposit value once prices were restored. [7] The attacker exploited Switchboard production code that governs who can sign oracle price updates, adding a key they controlled to a live oracle to push prices roughly 100 times below market. [8]
Proof8 sources · 2 publishers
What this stands on
  1. Switchboard, an oracle provider, said contributors halted its deployments on Aptos, Sui, IOTA, and Movement after reports of a potential compromise in its Move-language implementations. · cryptoslate.com
  2. Full Sail, a decentralized exchange on the Sui network, announced on September 1, 2026, that it is winding down operations after an attacker drained roughly $91,000 from three of its vaults on August 29. · beincrypto.com
  3. At least three applications reported losses, freezes, or precautionary access restrictions following the Switchboard incident. · cryptoslate.com
  4. Full Sail confirmed that its vaults lost funds and said deposits and withdrawals would remain paused until oracle integrity was restored and verified. · cryptoslate.com
  5. Virtue, an IOTA credit protocol, said an attacker gained control of the signing keys used by all 14 oracles on Switchboard's IOTA mainnet queue and pushed IOTA's reported price to $10 million. · cryptoslate.com
  6. Full Sail paused deposits and withdrawals after confirming the incident on August 29 and committed to returning funds to affected users while absorbing the shortfall. · beincrypto.com
  7. Full Sail stated that the attack was not an admin key compromise but involved direct liquidity pool positions, allowing the attacker to deposit funds and withdraw more than the deposit value once prices were restored. · beincrypto.com
  8. The attacker exploited Switchboard production code that governs who can sign oracle price updates, adding a key they controlled to a live oracle to push prices roughly 100 times below market. · beincrypto.com
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
Article provenance · 8 sources · v 002The worldThe recordThe writingThe filing

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Thursday, September 3, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
The automated line wrote this as TruthFoundry News Desk using a large language model at 2026-09-03T06:50Z.
The prompts, verbatim
System instruction (the grounding rules)


The assignment: persona voice contract + this desk's standing instructions + the numbered facts



4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.


Integrity


Content hash (SHA-256)fe20d3ce82f6c61717b8bd57ad0d2f3a2a7fe3f3ecf278a6413e0bfa1a8fcab0


Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed


Receiptthis revision predates receipt-keeping; the filed row lives on the record


Machine readablethe full proof, JSON


Verify



A signature proves who filed this and that it has not changed since. It never makes a claim true.