What Is a ‘Man-in-the-Middle’ Attack on a Centralized Oracle?

A man-in-the-middle attack on a centralized oracle occurs when an attacker intercepts and alters the data transmission between the centralized data source (like a stock exchange API) and the smart contract. The attacker essentially positions themselves between the two parties, providing the smart contract with a false price feed while the original source remains intact.

Since the contract only trusts the single data stream, it executes based on the manipulated price, leading to financial loss for the users.

What Is a “Man-in-the-Middle” Attack Risk for a Centralized Oracle?
What Is a ‘Data Feed’ in the Context of Decentralized Finance (DeFi)?
How Does a Multi-Source Oracle Architecture Mitigate Single-Point Risk?
What Is a ‘Request for Stream’ (RFS) and How Does It Compare to RFQ?
What Is the Risk of a Single-Source Price Feed Oracle?
What Is the Difference between a State Change and a Code Change in a Deployed Smart Contract?
What Is the Role of “Network Latency” in a Successful RBF Double-Spend Attack?
What Are the Risks Associated with a Single, Centralized Oracle Provider?

Glossar