Key Takeaways
- Pragma’s faulty oracle data led to 47 incorrect liquidations on Vesu lending protocol on September 4
- Approximately $3 million worth of user collateral was liquidated within a 120-second window
- Vesu maintains its smart contract infrastructure functioned properly with no exploitable flaws
- Pragma has implemented a solution while affected liquidity pools remain temporarily frozen
- Collaboration between Vesu and Starknet ecosystem partners aims to restore user funds
An erroneous oracle price feed supplied to Starknet’s Vesu lending platform resulted in the improper liquidation of 47 user positions, affecting roughly $3 million in deposited collateral on September 4, 2026.
The entire episode unfolded within a mere two-minute timeframe, specifically between 04:08 and 04:10 UTC, yet managed to create significant disruption throughout multiple liquidity pools on the platform.
The Root Cause of the Crisis
Vesu depends on Pragma’s oracle infrastructure to obtain accurate pricing information needed to evaluate the safety of outstanding loan positions. When Pragma delivered faulty price data, Vesu’s automated liquidation mechanisms incorrectly identified 47 positions as undercollateralized and eligible for immediate liquidation.
Automated liquidation bots subsequently seized control of roughly $3 million in user collateral during the brief window before Pragma’s price feed self-corrected. The inaccurate pricing persisted for under two minutes before reverting to legitimate market valuations.
The protocol has not yet revealed which specific tokens were impacted, the magnitude of price deviations from actual market conditions, or the exact amount of collateral seized by liquidators. Further clarification is anticipated in an upcoming comprehensive technical analysis.
Protocol Integrity Maintained, Says Vesu Team
Vesu emphasized that its underlying smart contract architecture was “functioning exactly as intended” and harbored no security vulnerabilities. The development team stated no code modifications were necessary since the liquidation system merely executed its programmed response to the corrupted oracle information.
In overcollateralized lending protocols, users pledge assets exceeding the value of their borrowed funds. The system continuously monitors the collateral-to-debt ratio using externally sourced price feeds. When a malfunctioning oracle indicates this ratio has fallen below the minimum threshold, automated liquidations trigger instantaneously.
Vesu characterized the September 4 incident as stemming from compromised data inputs rather than flawed contract logic.
Fund Recovery Initiatives in Progress
In the wake of the incident, Vesu initiated coordination efforts with Pragma, StarkWare, the Starknet Foundation, and liquidity pool curators to attempt fund restoration for impacted users.
The protocol has yet to specify what portion of the $3 million is recoverable or whether liquidation bot operators have consented to return any seized assets. No definitive compensation sum or distribution timeline has been publicly disclosed.
Affected users whose positions were eliminated during the critical two-minute period were instructed to submit support requests through Vesu’s Discord channel. Those utilizing the platform’s Earn products received guidance to maintain their existing positions, as premature withdrawals might jeopardize refund qualification.
Oracle Failures in DeFi: A Recurring Challenge
Oracle-related incidents remain a persistent vulnerability in decentralized finance. A comparable situation emerged on Aave during March 2026, where an outdated parameter triggered between $26 and $27 million in unwarranted wstETH liquidations. Aave subsequently reassessed its oracle refresh frequencies and backup mechanism designs.
Vesu has not disclosed plans for structural modifications to its oracle architecture apart from Pragma’s underlying issue resolution.
Smart contracts inherently lack the capability to independently access real-world market pricing. They maintain complete dependence on oracle networks to collect, consolidate, and transmit price information onto the blockchain. Any breakdown in this process can precipitate erroneous transactions or premature liquidations.
Vesu confirmed a detailed technical postmortem will be published following the completion of its internal investigation.


