The MultiHopOracle contract relies on external oracles for pricing data. If any of these oracles is compromised, malicious actors could manipulate the data returned by the oracle to produce incorrect results. Since the contract uses a sequential calculation method based on HopConfig, even a single manipulated oracle in the chain could significantly distort the final output.
Manipulated prices could lead to incorrect trades, unfair arbitrage opportunities, or systemic losses in dependent systems.
Invalid oracle data could cause calculations to revert or return unusable results, disrupting contract functionality.
Users may lose trust in the contract if it consistently produces incorrect results due to oracle manipulation.
Manipulated data combined with inversion (10 ** 36 / data) could amplify inaccuracies or distort results further.
Manual Code Review
Instead of directly chaining oracle data, use decentralized oracle networks (e.g., Chainlink) that aggregate data from multiple independent sources.
Reject suspicious or extreme oracle data using pre-defined thresholds or outlier detection.
Instead of relying on sequential calculations, aggregate data from multiple oracles (e.g., using the median or weighted average) to minimize the impact of any single manipulated oracle.
Reject oracle values that fall outside a predefined acceptable range, which could help ignore manipulated or extreme values.
Please read the CodeHawks documentation to know which submissions are valid. If you disagree, provide a coded PoC and explain the real likelyhood and the detailed impact on the mainnet without any supposition (if, it could, etc) to prove your point.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.