Two examples of malicious behaviour: (1) I have the server you're curling-into-bash. I write my server to check if it's piped into sh; if so, I instead pipe ma

Two examples of malicious behaviour: (1) I have the server you're curling-into-bash. I write my server to check if it's piped into sh; if so, I instead pipe malicious statements. (2) I have the server you're downloading from. I write the binary you're downloading so that it later executes malicious statements. The "don't curl into sh" is worried about the former. But, the latter seems a much more practical attack, that reading the script you curl is insufficient to protect you from. It seems weird to mention (1) without at least mentioning (2).