How Supply Chain Attacks Work: SolarWinds, XZ, and What's Next

One Compromised Vendor Can Expose 18,000 Organizations Simultaneously

In December 2020, FireEye (now Mandiant) disclosed that it had been breached by a sophisticated nation-state actor. The discovery unraveled a supply chain attack of unprecedented scale: Russian SVR hackers had inserted malicious code into the build process of SolarWinds' Orion IT management software. The trojanized software update was downloaded by approximately 18,000 organizations globally — including the U.S. Treasury, Commerce Department, State Department, and portions of the Pentagon. The attackers had undetected access for nine months before discovery. SolarWinds was not the target; it was the weapon. Every organization that trusted SolarWinds became an unintentional entry point.

The Anatomy of a Supply Chain Attack

Supply chain attacks exploit the trust relationships that modern software ecosystems depend on. Rather than attacking a target organization directly — which typically has substantial security investments — attackers compromise a trusted vendor, partner, or open-source project that the target relies on.

Case Study: The XZ Utils Backdoor (2024)

The XZ Utils incident revealed the patient, sophisticated approach of advanced supply chain attacks. XZ Utils is a data compression library used in many Linux distributions. Starting in 2021, a contributor using the pseudonym Jia Tan began making legitimate, valuable contributions to the project over two years — building trust, improving code quality, and gaining commit access. In early 2024, Jia Tan introduced a meticulously crafted backdoor into liblzma (a dependency of XZ Utils) through a series of commits obscured by binary test files.

The backdoor targeted specifically systemd-linked sshd processes on certain Linux distributions (Debian sid, Fedora Rawhide), potentially enabling unauthorized remote access. It was discovered in March 2024 by Microsoft engineer Andres Freund, who noticed unusual CPU usage and slow login times and investigated obsessively. The consensus among security researchers is that this was a nation-state operation, given its sophistication and the years-long investment in building a false identity with a credible track record.

Why Supply Chain Attacks Are Particularly Dangerous

• Scale: One compromised vendor can compromise thousands of downstream organizations simultaneously
• Trust exploitation: Malicious updates arrive through trusted channels — antivirus software, monitoring tools, and security products can themselves be vectors
• Detection difficulty: Legitimate software processes downloading and installing trusted vendor updates do not trigger typical security controls
• Dwell time: SolarWinds attackers had nine months of undetected access; XZ was undetected for months before accidental discovery
• Asymmetric investment: Attackers invest months or years in a single supply chain compromise that yields access to thousands of targets

Dependency Hell: The Open-Source Risk Surface

Modern software applications depend on hundreds or thousands of third-party libraries. A typical Node.js application may have 500–1,000 transitive dependencies — packages that the packages your code imports themselves import. Each dependency represents a potential attack vector.

Defensive Strategies for Organizations

• Software Bill of Materials (SBOM): A comprehensive inventory of all software components and dependencies in an application. Required for federal software procurement by U.S. Executive Order 14028 (2021). Enables rapid identification of affected systems when a vulnerable component is discovered.
• Vendor risk assessment: Evaluate the security practices of all critical software vendors — their development processes, access controls, code signing practices, and incident response capabilities.
• Code signing verification: Verify cryptographic signatures on all software updates before installation. Establish baseline signatures for critical software.
• Dependency pinning: Lock dependency versions to specific, audited releases rather than accepting automatic updates.
• Network segmentation and least privilege: Even if a supply chain attack succeeds in gaining a foothold, network segmentation limits lateral movement and least privilege limits the damage of any single compromised system.
• Behavioral monitoring: Anomaly-based detection systems that identify unusual behavior from legitimate processes — like SolarWinds software making unexpected outbound connections — can catch supply chain attacks that signature-based tools miss.

The Future of Supply Chain Security

The security community's response to supply chain attacks includes SLSA (Supply-chain Levels for Software Artifacts), a framework developed collaboratively by Google and the broader industry defining security guarantees for software build processes at four levels. SIGSTORE provides free, open-source infrastructure for code signing and verification. The U.S. government's Secure Software Development Framework (SSDF) establishes baseline software security practices for federal contractors. These initiatives represent a systemic attempt to raise the baseline security of software development across the industry — recognizing that individual organizations cannot defend against supply chain attacks without industry-wide infrastructure improvements.