Incident Overview
On January 3, 2026, Valinity DeFi suffered a $63,000 exploit due to a business logic flaw in its rebalancing mechanism.
The vulnerability stemmed from a business logic flaw rather than simple price manipulation in Valinity's rebalancing system. VY token functions as a synthetic asset that users can utilize as collateral to borrow BTC, ETH, and PAXG. The protocol implements an anyone-can-call function named acquireByLTVDisparity designed to rebalance VY holdings based on LTV ratios and Uniswap V3 spot prices, but this function was hardcoded to swap VY tokens into a near-empty liquidity pool containing approximately $106 USDC.
The attacker exploited this by first swapping USDC to PAXG, artificially driving the PAXG price higher rather than lower as typical price manipulation attacks would do. When the rebalance function was called with the elevated PAXG price, the contract automatically dumped VY tokens into the tiny liquidity pool at unfavorable rates. The attacker then purchased these undervalued VY tokens from the pool and used them as collateral to borrow ETH, BTC, and PAXG, successfully exiting with the stolen funds.
Following detection, Valinity immediately paused its contracts by disabling all borrow functions to prevent further exploitation.
Incident Report
Protocol Information
What the Attacker Needed to Succeed
Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.
What Auditors Should Check
If you're auditing a protocol with similar architecture to Valinity, these are the critical security checks that could have prevented this incident (January 2026).
- Verify all logic paths related to Oracle Issue are guarded by proper access controls and input validation - see the Oracle Manipulation & Price Manipulation attack class for patterns
- Audit oracle price feeds for manipulation risks - ensure time-weighted average prices (TWAPs) or multi-source aggregators are used, not spot prices
- Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs
Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.
Free TrialRelated Attack Classes
The technique used in this hack maps to these vulnerability classes in our security curriculum:
Sources & References
- 01
Learn to Prevent the Next Valinity
The Valinity hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.