The attacker submitted illegitimate price reports that appeared valid, rapidly opening and closing positions to extract an artificial profit from the vault.
Recovery operations active
Protocol recovery,
transparently.
Following the July 15 OLP vault incident, the focus is on securing infrastructure, reconciling impacted liquidity providers, and returning funds through a verifiable recovery process.
Recovery verification will never ask for a seed phrase or private key.
Reported vault impact$23.75MUSDC under investigation
Trader collateralIsolatedHeld in a separate contract
Recovery processOnchainAllocation records will be verifiable
Claim statusPreparingNo action required yet
01 / Incident update
An update on where things stand.
The OLP liquidity-provider vault was affected by manipulated price reports originating from compromised offchain infrastructure. The protocol response is focused on containment, independent investigation, and a secure path to restitution.
Affected operations were paused, infrastructure was isolated, and investigation work began with security specialists and law enforcement coordination.
Impacted LP balances are being reconciled before claim allocations and a safe resumption plan are published.
02 / Restitution
A clear path back to whole.
Connect the wallet that held OLP at the incident snapshot. Wallet ownership is used to verify eligibility, display the recovery allocation, and prepare the USDC return claim.
Wallet not connected
Connect the wallet used for your OLP position
No transaction is sent during verification.
Recovery allocationConnect wallet
--USDC
- Snapshot balance
- Pending
- Recovery ratio
- To be published
- Distribution network
- Arbitrum
03 / Safeguards
Verify first.
Sign only when ready.
A legitimate recovery flow should be easy to audit and difficult to spoof. Every published step must be independently verifiable before a wallet interaction is enabled.
No seed phrases
Ostium recovery will never require a private key, seed phrase, or remote access to a device.
Public contracts
Distribution contracts and allocation methodology should be published before claims open.
Simulate first
Users should be able to inspect every transaction before signing or granting permissions.