On June 2025, GradientMakerPool was exploited in a oracle manipulation, resulting in approximately $5K in losses. That makes the GradientMakerPool exploit the 410th largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the GradientMakerPool Oracle Manipulation Played Out
Exploit Class Applied to GradientMakerPool
The GradientMakerPool incident on June 23, 2025 is classified as a Oracle Manipulation. The attacker skews the price feed the protocol trusts — often via a thin DEX pool — forcing the contract to misprice collateral. In the full archive, GradientMakerPool is 1 of 19 documented oracle manipulation incidents.
GradientMakerPool in Context
At $5K, the GradientMakerPool exploit is a minor (<$1M) event compared to the largest same-class incident in our archive — – BonqDAO (2023) at $88M.
Prior Oracle Manipulation Before GradientMakerPool
The nearest oracle manipulation incident before GradientMakerPool was ImpermaxV3, 58 days earlier on April 26, 2025 ($62.6K lost). The same exploit class surfaced again within the oracle manipulation attack surface.
GradientMakerPool Vulnerability Signature
The primary source categorises the GradientMakerPool exploit specifically as “Price Oracle Manipulation”. This narrower label is entity-specific: it reflects how the GradientMakerPool contract failed, rather than the broad oracle manipulation pattern alone.
Impact & Recovery for GradientMakerPool
GradientMakerPool Loss Figure
The GradientMakerPool exploit caused $5,000 in losses — a minor (<$1M) incident and the 76th largest of 96 documented in 2025.
Where GradientMakerPool Sits Among Oracle Manipulation Attacks
Ranked by loss size, GradientMakerPool is the 8th largest of 19 oracle manipulation incidents documented. That puts the GradientMakerPool loss below the class average of $9.69M.
Timeline Since the GradientMakerPool Incident
The GradientMakerPool exploit occurred 10 months ago (295 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for GradientMakerPool
Public post-mortem / on-chain analysis for the GradientMakerPool incident: view source.
FAQ
How much did GradientMakerPool lose?
The GradientMakerPool exploit in June 2025 resulted in $5,000 in losses — the 76th largest of 96 DeFi incidents that year.
When did the GradientMakerPool hack happen?
The GradientMakerPool exploit was recorded on June 23, 2025 — 295 days ago.
What type of exploit hit GradientMakerPool?
The GradientMakerPool incident is classified as a Oracle Manipulation. The attacker skews the price feed the protocol trusts — often via a thin DEX pool — forcing the contract to misprice collateral.
How common is the Oracle Manipulation pattern seen at GradientMakerPool?
Our archive contains 19 documented oracle manipulation incidents. The GradientMakerPool incident is one of them.
How does GradientMakerPool compare to the largest Oracle Manipulation attack?
The largest oracle manipulation incident in our archive is – BonqDAO (2023) at $88M. The GradientMakerPool loss is $5K.
Which machine learning model is highlighted as the best-performing for cryptocurrency price prediction?
Long Short-Term Memory (LSTM).
What potential benefits does the integration of AI and blockchain offer to cloud manufacturing?
Benefits include improved risk management, enhanced operational efficiency, and the facilitation of secure, transparent collaborations between manufacturers.