LANGUAGES Signal 284 2 feeds carried it
Researchers demonstrate trusting-trust attack via GNU strip in NixOS bootstrap process
↗
Illustration only Photo by Kier in Sight Archives on Unsplash
A proof-of-concept attack shows that Ken Thompson’s trusting-trust technique can propagate through binary manipulation of GNU strip, backdooring an entire Linux distribution without touching source code or compilers.
This extends the scope of trusting-trust beyond compilers to ordinary build utilities, forcing engineers to re-examine every binary in the bootstrap chain. The attack survives rebuilds and backdoors nearly all binaries in the final environment, making detection and mitigation far harder than previously assumed.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
The attack uses GNU strip, a utility that neither inspects nor generates source code, to implant a payload in ELF binaries.
A single tampered strip binary in the NixOS bootstrap seed propagates the backdoor across generations and into the final standard environment.
On a real nixpkgs revision, the attack backdoors almost every binary in a complete graphical installer without build failures.
THE READ
What the cluster adds up to.
The paper demonstrates that the classic trusting-trust attack is not limited to compilers. By targeting GNU strip, a utility that manipulates ELF binaries post-compilation, the authors show that any binary in the build chain can serve as a vector. This shifts the threat model from source-level tampering to binary-level persistence, which is harder to audit and detect.
The attack exploits the NixOS bootstrap process, where a single compromised strip binary in the initial seed propagates its payload through subsequent rebuilds. The backdoor survives even after the seed leaves the dependency closure, embedding itself in the final standard environment. This persistence means that traditional rebuilds or source audits will not remove the infection.
In practice, the attack backdoors nearly every binary in a complete graphical installer built from a real nixpkgs revision. The build completes without failures, making the compromise invisible to standard CI/CD checks. The scale of the backdoor, affecting almost all binaries, demonstrates that even minor utilities can have outsized impact if they are part of the bootstrap chain.
Mitigation is non-trivial. The attack does not require source code access or compiler manipulation, so existing defenses like reproducible builds or source audits are insufficient. Engineers must now treat every binary in the bootstrap chain as a potential threat vector, increasing the complexity of securing build environments. The paper does not propose a solution, but it makes clear that the problem is broader than previously understood.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER