Why this malicious behavior of corrupted sender isn't considered in malicious-secure OT? I have read some oblivious transfer protocols, and I am confused about why they do not mention the malicious behavior that the corrupted sender may encrypt the wrong message $x_0'$ and $x_1'$ so that the honest receiver will receive the wrong result $x_\sigma'$. I think this totally breaks the correctness of OT and I don't know why the malicious secure OT protocol did not mention it. I know that the committed OT can prevent this behavior, but is this not a malicious behavior that one malicous-secure OT should consider?
In MPC we judge security by comparing to the "ideal world" where a trusted third party does the entire computation. In the ideal world, an adversary can send anything it wants as input to the trusted third party. In the ideal world, when it comes to malicious adversaries, there really is no valid sense of a "correct/incorrect input" for the adversary. (For semi-honest adversaries, their input is supplied by the external environment and they are bound to use it in the ideal world.) Since "using whatever input you like" is possible on the ideal world, it is not considered an attack against the protocol.