The figure worth focusing on is 0.494, not 4.94 million. With the feed reporting ten million dollars per IOTA [3], the roughly 4.94 million VUSD minted through Virtue [4] is covered at par by 0.494 tokens of nominal collateral [1], and because CDP designs make you post more than you borrow [15], the requirement scales with the ratio rather than with the notional, so a 150% requirement would have needed 0.741 tokens [2] (Crypto Briefing does not publish Virtue's actual ratio, so treat that second figure as illustration). Either way the capital requirement rounds to pocket change, since the scarce input here was signing authority rather than collateral [9].
Set that against the 2022 Mango Markets exploit, where an attacker had to move a real price on a real market and extracted $114 million [13]. The IOTA mint came to about 4.3% of that damage [3] with none of the trading. The more interesting comparison is that the cost side collapsed to nearly nothing while the loss side was bounded only by what Virtue happened to be willing to mint.
Whether that generalises is the live question. The halt went out across the August 28 to 29 transition [2], and Crypto Briefing reads the decision to stop all Move-based implementations as a sign the vulnerability may be architectural rather than specific to one network [6]; the shared lineage is real, since Move came out of Meta's Diem project and now sits under Aptos, Sui, Movement and IOTA's newer infrastructure [7]. But three of the four halted chains have no confirmed loss [4], Switchboard's own position is that funds are intact beyond IOTA [12], and it says it is working with security agencies on the investigation [14].
Either a single operator credential leaked and the four-chain halt is precaution, in which case feeds come back within days and nothing about the code changes; or the signing infrastructure is shared across the Move deployments, in which case halting all four was the minimum honest response and the diligence question for every integrator moves from how deep the market is to who holds the key and in what hardware; or the flaw is in the Move implementation itself, which is the reading most consistent with a Solana branch on separate code being left running while its users are still told to find another feed for now [8].
This is probably wrong, but I would put weight on custody over language, because a key that can rewrite a price directly [9] does not need an architecture to be interesting. What would prove it wrong is a postmortem naming a code path in the Move build, or a resumption on Aptos and Sui with no disclosed change to key handling, which would mean 45 users [5] absorbed the cost while the underlying vulnerability went unaddressed.
The bill lands as engineering time and dead books. Protocols wired to a single Switchboard feed cannot process liquidations or update collateral ratios until service returns [10], so their next sprint is incident response instead of product, while the ones already paying for Pyth, Chainlink or Redstone alongside it keep trading [11]. The mint works out to about $109,800 of VUSD per directly liquidated user [5], which is not what each of them lost but is the right order of magnitude for what a second feed would have been worth on the day.
