Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Those who caught it were indeed very clever. But the attacker did make mistakes, particularly the Valgrind issues and large performance regression. That ultimately is what raised suspicions.


The large performance regression was a feature of the string obfuscation.


Interesting! So perhaps not really effective obfuscation after all!


"Large" is doing quite a bit of work here: the engineer who found it had disabled turbo boost and was, by at least a little serendipity, quite performance focused at the time rather than being busy on other elements of their release target.


A 0.5s additional delay added to SSH is HUGE. No way this would not have been noticed sooner or later.


This is why I think it all came falling down due to the teknoraver patch to libsystemd to replace lzma with libarchive.

Because anyone has the resources to test this locally and find the issues, but they just didn't have the time anymore.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: