Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

How the SolarWinds Orion Backdoor Worked

The SolarWinds Orion backdoor, known as SUNBURST, was signed malicious code shipped inside legitimate software updates, reaching roughly 18,000 organisations before its discovery in December 2020.

Illustration for the cybersecurity term SolarWinds Orion Backdoor
Home / Blog / Cybersecurity Terms / How the SolarWinds Orion Backdoor Worked
17 November 2026

How the SolarWinds Orion Backdoor Worked

How the SolarWinds Orion Backdoor Worked

On 13 December 2020, SolarWinds confirmed that updates to its Orion network monitoring platform had been shipping with a backdoor inside them. The malicious code, named SUNBURST by Mandiant and Solorigate by Microsoft, sat in a legitimate component of the product, carried a valid SolarWinds digital signature, and was distributed through the vendor’s own update channel. Around 18,000 customers installed an affected build.

In April 2021, the UK and US governments jointly attributed the operation to Russia’s Foreign Intelligence Service, the SVR, the actor tracked as APT29. It remains the reference case for what a software supply chain attack can achieve.

Subverting the Build, Not the Source

The attackers did not simply commit malicious code to a repository, where a reviewer might have seen it. They placed an implant called SUNSPOT on a SolarWinds build server. SUNSPOT watched for MSBuild processes compiling the Orion solution and, for the few seconds that the relevant source file was being read, swapped it for a version containing the backdoor. Once compilation finished, the original file was restored.

The result was a build whose source control history looked clean and whose output was signed by the genuine code-signing certificate as part of the normal release process. The malicious component, SolarWinds.Orion.Core.BusinessLayer.dll, appeared in Orion Platform versions 2019.4 HF5 through 2020.2.1 HF1, released between March and June 2020.

Patience as an Evasion Technique

SUNBURST was written to look unremarkable:

Only a small subset of victims, estimated at fewer than a hundred organisations plus nine US federal agencies, received a second stage. Those received loaders known as TEARDROP and RAINDROP, which delivered Cobalt Strike Beacon for hands-on-keyboard activity.

What the Attackers Did Next

Inside selected victims, the operators concentrated on identity. They stole Active Directory Federation Services token-signing certificates, then forged SAML tokens to authenticate to cloud services as any user, including administrators, without touching the password or the second factor. This technique, later nicknamed Golden SAML, meant that cleaning the on-premises network did not necessarily end the intrusion.

They also added credentials to existing application service principals in Microsoft 365 tenants, giving themselves persistent mail-reading access that survived user password resets. Discovery came from the outside: FireEye found the intrusion while investigating the theft of its own Red Team tooling and published its analysis on 8 December 2020.

Why Detection Took Nine Months

Orion is a monitoring platform. It holds credentials for routers, switches, hypervisors, and servers, it is expected to talk to everything, and it is routinely excluded from endpoint monitoring to avoid performance complaints. A backdoor inside it inherits all of that trust. Code signing, which most organisations treat as an integrity guarantee, confirmed only that SolarWinds had built the file, which was true.

What Changed Afterwards

The incident reshaped supply chain expectations rather than any single control:

The practical lesson for defenders is narrower than it first appears. You cannot verify a vendor’s build server, but you can limit what their software is allowed to reach: segment management platforms, restrict their outbound internet access to documented destinations, monitor the DNS they generate, and apply least privilege to the service accounts they run under.

At Privia Security, we test exactly those assumptions during Infrastructure and Architecture Review Services, starting with the management tools that sit above everything else.

FAQ – Frequently Asked Questions

Which SolarWinds Orion Versions Contained the Backdoor?

Orion Platform versions 2019.4 HF5 through 2020.2.1 HF1, released between March and June 2020, contained the trojanised SolarWinds.Orion.Core.BusinessLayer.dll component. SolarWinds published hotfixes 2020.2.1 HF2 and later to remove it. Organisations that installed an affected build were advised to treat the host as compromised, rebuild it, and rotate every credential the platform had stored.

Did a Digital Signature Fail to Help Here?

Code signing worked exactly as designed and still did not help. The signature proved the file came from SolarWinds and had not been altered after signing, both of which were true. Because the malicious code was inserted before the signing step, the signature certified the backdoor. Signatures verify origin and integrity, never the intent of what was built.

What Is Golden SAML and Why Did It Matter in This Incident?

Golden SAML is the forging of federation assertions using a stolen ADFS token-signing certificate. With that certificate, an attacker can mint tokens for any user in any federated application, bypassing passwords and multi-factor authentication. In this case it let the operators keep cloud access even after on-premises remediation, which is why certificate rotation became a required recovery step.

How Can a Smaller Organisation Reduce Supply Chain Risk Like This?

Assume that some vendor software will eventually be compromised and limit the consequences. Place management and monitoring platforms in their own network segment, allow only documented outbound destinations, log and review their DNS queries, give their service accounts the minimum rights required, and keep an accurate inventory so you can answer the question of exposure within hours rather than weeks.

Related Terms

You May Be Interested In These

What Is API Penetration Testing?

Cybersecurity Terms

17 November 2026

What Is API Penetration Testing?

Read More
What Are Plaso and log2timeline?

Cybersecurity Terms

17 November 2026

What Are Plaso and log2timeline?

Read More
What Is Password Spraying?

Cybersecurity Terms

17 November 2026

What Is Password Spraying?

Read More