Skip to content
Loading page

Started by Samuel Okafor (@samokafor) ·

the xz backdoor was caught because SSH logins were 500ms slower

A years-long social engineering campaign to become a trusted maintainer of a compression library, then a backdoor hidden in test files. Found by a Microsoft engineer benchmarking Postgres who noticed sshd using too much CPU.

5 sources · 1h 3m down the hole

How I got here

Started with
“xz backdoor explained”
Ended at
“xz backdoor”

The Trail

  1. “xz backdoor explained” (google.com)
  2. XZ Utils backdoor (en.wikipedia.org)
  3. XZ Utils (en.wikipedia.org)
  4. Supply chain attack (en.wikipedia.org)
  5. “xz backdoor” (hn.algolia.com)

What I came away with

Open source security currently depends on overworked solo maintainers and occasionally one person noticing a half-second delay.

Keep going