News for hackers. Stuff that matters.
Re:Detecting the use of “curl | bash” server side by nodoodles on Tuesday December 27, 2022 @03:20AM (#34146524)
Neat! A more foolproof method might be sending a bit of bash that triggers a callback request (ie "liveness check", "latest version check" etc) to origin server, and pauses.

When the callback is received, continue with malicious payload, otherwise after some timeout, send a benign script..

Re:Detecting the use of “curl | bash” server side by jameshart on Tuesday December 27, 2022 @09:47AM (#34149096)
This approach seems much simpler and more reliable than detecting the pipe buffer is full.
Re:Detecting the use of “curl | bash” server side by catalypso on Tuesday December 27, 2022 @10:27AM (#34149445)
That would indeed be more precise, but it would be harder to obfuscate.

If I simply curl the script (without piping to bash), I'd be less suspicious if I saw a sleep than I would be if I saw a callback to a server.