Sometimes you accidentally "cat" a binary... only for your terminal to become utterly corrupted, ending up in another code page where all characters are unrecognizable, while your shell spits back at you "Command not found" "Command not found" as if you tried to execute something.
So, how can this be used in exploits?
And how can it be prevented?
And how did it end up for this to be possible in the first place?
It seems obvious that what's happening behind the scenes is that your terminal think that it is prompted for its identity, and then responds at the wrong time. But what if you had a "sleeper" shell script by that name, that re-opened a back-door or pinged someone that a careless user was at the terminal of whatever device?
