As a nix user, I wouldn't laugh. We are vulnerable to this type of attack as well.
Heck, it's surprising we aren't full of malware considering how many packages there are, and an easy supply chain attack vector with auto RyanTM PRs.
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
As a nix user, I wouldn't laugh. We are vulnerable to this type of attack as well.
Heck, it's surprising we aren't full of malware considering how many packages there are, and an easy supply chain attack vector with auto RyanTM PRs.
Yea. especially if you use flakes heavily. Itβs so decentralized it could take longer to catch.
It's possible, but at the very least someone glances over the derivation since it's part of the actual nixpkgs repo right? AUR on the other hand is a wild west.
is a wild west.
I prefer to call it anarchy
Yeah if the url is https://i_hack.you/ yeah that will be easy to spot. But imagine an attacker just to a "patch update", updating the url and hash to the malicious repository, and use a typo squatted domain/repository, that will make it harder to spot.
No, it would actually be quite easy to spot.
Nixpkgs templates the source code url fro the url, and then it injects a variable
Here is an example from bash:
pname = "bash${lib.optionalString interactive "-interactive"}";
version = "5.3${fa.patch_suffix}";
patch_suffix = "p${toString (builtins.length upstreamPatches)}";
src = fetchurl {
url = "mirror://gnu/bash/bash-$%7Blib.removeSuffix fa.patch_suffix fa.version}.tar.gz";
hash = "sha256-DVzYaWX4aaJs9k9Lcb57lvkKO6iz104n6OnZ1VUPMbo=";
};
If the url were to be changed, it would show up as a change in git when someone is reviewing before merging.
Yes, on one hand every commit to nixpkgs needs review (to some degree) on the other hand there are far too many committers to nixpkgs.
There are also gaps such as the bots to auto-merge packages with maintainer approval, so a simple attack looks like this:
So nixpkgs is better than the AUR, but it isn't great and unlike Arch has no separate official repos.
I remember when, I think it was either a log4j or CUPS malware attack, Debian remained unaffected because the packages in its repos was too old.
debian stable misses a lot of the 'fun'.
That's why it's the best.
Slow and steady wins the race
Laughs in Debian
The term "hacked" seem to have lost all meaning...
This happened long ago. Before even this
Well... People finding and disclosing security flaws are often much closer to hackers than what happened with the AUR.
Calling people adopting outdated and orphanded packages hackers is like calling the guy that finds a banknote on the ground a bankrobber.
Oh right THAT fucking thing
AUR: it happened to me, and one day it will happen to you!

This is still the shai hulud worm.
Thereβs no reason nixpkgs hasnβt been hacked yet. It jest depends on a few devs credentials being stolen, either by vscode, an npm package, a pypi dep, etc.
Comparing the AUR to nixpkgs is like comparing the NUR and random flakes to the main Arch repositories.
Had the AUR been prefixing the package names with the maintainer name like the NUR does, then it would not be possible to do the orphan adoption attack at the same scale. (Instead a bunch of duplicates with higher version numbers would pop up, prompting users to switch)
Running both ... Nixpkgs will rightfully laugh about this - in about a month once they caught up on recent events.
Loving both arch and nixos though!
They're already laughing in master, it will be merged to stable right after the current stable branch is fixed because half of packages fail to build (again).
COPR: "You guys are actually sharing your packages with other people?"
I mean, no one is stopping you from using Nix on Arch
I believe I even got the reverse, pacman working on Nix (I've also gotten it and archiso working on Fedora)
You... Monster.
Can you add aur to pacman?
I didn't think you could, but TBH I only use arch on the side ( or by the way , if you will) mostly debian. I dunno i'd want to put aur into pacman even if i knew how.
Y'all just haven't noticed yet.
We're any chaotic-aur packages affected?
Not to my knowledge. They did block a few of these because they got auto-flagged for manual review.
Thanks
If they compiled updated versions of affected packages then yes