it prompts for elevated permissions on install, additionally most package managers like ArchLinux yourt include the binary as setuid root. I discovered this bug while hacking on the defcon2018 badge.
Worth noting that it's a third party package outside the officially repositories for people that aren't familiar with that. Lots of those unofficial packages make bad decisions, although they're just packaging the results of the installer in this case.
Sure, this is what's happening, but it's irresponsible on the distro's part. A modern distro should have a pretty absolute policy of no suids outside the core packages, or at least not in contrib packages that aren't subject to the level of review main-repo ones are.
It's a completely third party package, not one in a distribution contrib repository. Third party packages can be outright malicious and it doesn't even need to be subtle. It's a bad idea to use AUR helpers like yaourt since they encourage blindly trusting third party code.
I'd recommend using one like auracle simply downloading the PKGBUILD sources and always just treating it as a starting point for making your own packages. It's user generated third party content, not a distribution repository. You could make an account right now and upload one.
I definitely think many users end up blindly trusting the AUR even though the distribution makes it clear it's user generated content.
https://wiki.archlinux.org/index.php/Arch_User_Repository…
If someone abandoned a popular package, I expect many lazy people could be compromised by an attacker taking it over.
But I think it's reasonable to say that users do not generally know, and should not be expected to know, whether third-party package installers run poorly-vetted or unvetted code as root. The package install systems should be designed such that they can't.