WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2025 Poal.co

942

(post is archived)

[–] 2 pts

The is frightening. This would be an excellent Obfuscated-shell entry. The payload is hidden in the test xz files in the distribution. So convenient that it's a decompressor thus they can hide it in corrupt files (which are corrected then decompressed).

[–] 2 pts

The only suspicious thing about the test files is that there were no new tests added that used them in the same commit that added the files. It would have taken some manual garbage cleanup later for anyone to realize those test files were not referenced anywhere in the repo. I guess that’s a new thing to check for: unreferenced binary blobs.

[–] 1 pt

Fun fact: The only thing I’ve ever used xz for directly is to run a process that causes CPU activity for performance testing.

xz -6c /dev/urandom > /dev/null &

Run that once for each CPU core you have and listen to your fans spin up to full speed.

[–] 0 pt

Looks like you dodged a bullet there. It seems like a lot of people could have been caught out by this.

What we know about the xz Utils backdoor that almost infected the world | Ars Technica https://arstechnica.com/security/2024/04/what-we-know-about-the-xz-utils-backdoor-that-almost-infected-the-world/

[–] 1 pt

I only dodged this because my distro didn’t happen to upgrade to this version of xz. My machines run OpenSSH like almost everyone’s and they use xz under the hood.

[–] 0 pt

Accidentally got it right still counts :p