Back to blog
Famous hackssupply chainAPT

SolarWinds 2020: The Supply Chain Attack That Changed Everything

Published on 2026-04-059 min readFlorian

The Attack That Redefined Supply Chain Threats

In December 2020, cybersecurity firm FireEye revealed it had been breached. The investigation led to a far graver discovery: the SolarWinds Orion network management software, used by 33,000 organizations including major corporations and U.S. government agencies, had been compromised at the compilation level.

How the Attack Worked

Step 1: Build system compromise. The attackers (attributed to the Russian group Nobelium, also known as APT29 or Cozy Bear) infiltrated SolarWinds' development environment. They modified the build process to inject a backdoor into Orion's source code.

Step 2: The SUNBURST backdoor. The malicious code, named SUNBURST, was embedded in a legitimate DLL (SolarWinds.Orion.Core.BusinessLayer.dll). It was digitally signed by SolarWinds, making it undetectable by standard security tools.

Step 3: Distribution via updates. Between March and June 2020, Orion updates containing SUNBURST were distributed to approximately 18,000 organizations through SolarWinds' official update mechanism.

Step 4: Selective activation. SUNBURST did not activate on all installations. It remained dormant for about two weeks, then communicated with a C2 (Command and Control) server via DNS. Attackers then selected high-value targets for deeper access.

Step 5: Post-exploitation. On selected targets, attackers deployed additional tools (TEARDROP, RAINDROP) to steal data, access emails, and pivot within the network.

Victims

Of the 18,000 organizations that installed the compromised update, approximately 100 were actively exploited. Among them: the U.S. Treasury Department, the Department of Homeland Security, the Department of Justice, Microsoft, Intel, Cisco, and dozens of Fortune 500 companies.

Why It Was Nearly Undetectable

SUNBURST was exceptionally well-crafted:

  • It was signed by a legitimate SolarWinds certificate
  • It waited two weeks before activating
  • It communicated via DNS, a protocol rarely blocked
  • It checked for security tools and did not activate if certain ones were detected
  • It mimicked legitimate Orion traffic
  • Lessons

    The software supply chain is a strategic attack vector. Compromising a software vendor allows reaching thousands of targets in a single operation.

    Digital signatures do not guarantee integrity. If the build process is compromised, malicious code will be signed just like legitimate code.

    Detection must go beyond signatures. Sophisticated backdoors require behavioral analysis, not just signature detection.

    Zero trust is not a marketing concept. If SolarWinds Orion (a network management tool with elevated privileges) is compromised, the perimeter security model collapses.

    SolarWinds changed how the industry thinks about software supply chain security. Organizations that regularly audit their dependencies and exposed services are better prepared. That is exactly what CleanIssue verifies during its audits.

    Related articles

    Three adjacent analyses to keep exploring the same attack surface.

    Sources

    Written by Florian
    Reviewed on 2026-04-05

    Editorial analysis based on official vendor, project, and regulator documentation.

    Related services

    If this topic maps to a real risk in your stack, these are the most relevant CleanIssue audits.

    Need an external review of your HR SaaS?

    Share your product, stack, and client context. We will come back with the right review scope.

    Discuss your audit