Switchboard confirmed, per reporting by Blockonomi, that operations on Aptos, Sui, IOTA, and Movement were suspended after contributors flagged a potential compromise affecting the network's Move-based deployments. The blockchains themselves remain operational — the suspension applies only to the oracle infrastructure layered on top.
The shared instruction set
The four suspended deployments share more than geographic proximity — they share the Move instruction set. Move, originally developed at Facebook for the Diem project, became foundational to Aptos and Sui, and was later adopted by IOTA through its Rebased upgrade, which reached mainnet in May 2025. That shared programming environment does not establish that Move carries the vulnerability. It does, however, compress the investigation surface: any defect, dependency, or signing procedure embedded in Switchboard's Move-based implementation propagates uniformly across each affected chain. The provider has not confirmed whether the IOTA incident explains the full scope of the compromise. Its initial disclosure identified no root cause, no attacker, no confirmed losses, and no count of affected applications. A technical postmortem has not been published. Meanwhile, no similar reports have surfaced involving the provider's Solana implementation, which sits entirely outside the Move dependency tree.
The Virtue transaction sequence
The proximate trigger traces to an IOTA incident in which an allegedly compromised oracle key reportedly pushed an asset price feed to $10 million. The distorted valuation propagated through Virtue, a collateralized debt position protocol on IOTA, where users mint VUSD by depositing assets such as IOTA and stIOTA as collateral. The attacker minted approximately 4.94 million VUSD against collateral whose apparent value had been inflated by the corrupted feed, after which liquidations cascaded across roughly 45 user positions before the incorrect data was removed. The sequence — inflated price attestation, debt issuance against distorted collateral, liquidation enforcement at inflated valuations — is the canonical failure mode of any price oracle path whose authorship can be unilaterally co-opted by a compromised key.
Viability and migration
The protocol remains functional on non-Move chains. The Move-based deployments have entered an indeterminate safety state pending contributor verification, and users are being advised to temporarily migrate to alternative oracle solutions while the investigation continues. The cascade pattern — a single compromised key producing minting events and forced liquidations across dependent protocols — mirrors the failure mode seen in the parallel Term Labs governance breach that drained $8.5 million, underscoring how narrowly decentralized finance rests on the liveness and integrity guarantees of a small set of external data publishers.