The website owner can determine if you are just downloading to investigate script or if you are downloading and running.
In the last scenario the owner can decide to give you bad code and you won't know what happened / can't prove that the website owner did anything to you.
With APT the owner cannot see which case it is in, someone can always investigate what is being published by just downloading a package.
Otherwise, as you noted - if you trust the wrong person you will get owned either way, but curl|bash is inherently more dangerous due to easy targeting.
(I can push a package in apt via curl|bash too so it gets upgrade regularly)
The author hints at other techniques for detecting curl|bash (http or dns callbacks), which would obfuscate but not completely mask the attacker's intentions.
Note that I'm not advocating for using curl|bash: it's a technique for gathering low-hanging fruit, and there's no point in putting yourself in that position.
- browser crash
- I reload last website
- crash again
- I know that site has an exploit - so I try curl to get the payload - it's no longer there.
- I set up wireshark - open up in browser - exploit no longer there.
I'm now stuck with no way to figure out what happened, core dump is useful to prevent the crash but not find the code that triggered it.
So disconnect / fresh install OS.
This kind of targeting can happen now with curl|bash detecting if you install or just download.