Ostium reported that attackers obtained an oracle signer private key and used it to drain about $23.75 million from its liquidity vault. The protocol’s trading and vault logic trusted the signed price inputs that the compromised key produced.
This incident shows how oracle systems can become a single point of failure. If a protocol assumes signed data is trustworthy but the signer key is stolen, the on-chain logic will accept invalid information as legitimate.
Defenses include multiple independent oracle signers, hardware-backed key protection, rapid key rotation, and circuit breakers that halt trading when price behavior becomes abnormal. Protocols should also separate trader collateral from shared liquidity wherever possible.
Monitoring should look for unusual signing patterns, future-dated messages, or deviations from expected feed behavior so a compromised signer can be isolated before the vault is emptied.