Packet Path/

SolarWinds Orion: The Signed Update That Carried a Back Door

Between March and June 2020, Orion updates left SolarWinds carrying something SolarWinds had not written: a back door added when its build system was compromised, then signed with SolarWinds' own legitimate certificate so customers' systems trusted it. SolarWinds told about 33,000 Orion customers on December 13, 2020, and said fewer than 18,000 may have had an installation containing the vulnerability. CISA ordered federal agencies to disconnect affected devices the same day — and was clear that having the back door delivered was not the same as being targeted afterwards. This is the documented story, from CISA Alert AA20-352A and SolarWinds' December 14, 2020 SEC filing.

Case Studies · Intermediate · 12 min · November 15, 2026

Editorial illustration on a dark teal background: a network monitoring dashboard with a world map of watched devices, one software update package glowing in the centre with a small hidden door open on its side and a thin dotted line leaving it toward a distant shadow.

The short answer

In 2020, attackers compromised the system SolarWinds used to build its Orion network-monitoring software, and inserted a back door — a hidden way back into a computer — into Orion updates released between March and June 2020. The malicious code was not in SolarWinds' source code (the human-written code its engineers keep). It was added during the build, and the finished update was then signed with SolarWinds' legitimate code-signing certificate — the digital stamp customers use to check that software really came from the vendor. So the poisoned update passed the trust check. On December 13, 2020, SolarWinds told approximately 33,000 Orion customers, and said it believed fewer than 18,000 may have had an installation containing the vulnerability. The same day, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) ordered federal civilian agencies to disconnect affected devices. CISA is explicit on the point most retellings blur: not every organisation that received the back door was then targeted with follow-on actions. On April 15, 2021, the U.S. Government attributed the activity to the Russian Foreign Intelligence Service (SVR).

The company: what SolarWinds did

SolarWinds makes software that helps IT teams watch and manage their networks, systems, and infrastructure. In its December 14, 2020 filing with the U.S. Securities and Exchange Commission (SEC), the company said it valued the privacy and security of its over 300,000 customers.

The product at the centre of this case is Orion, SolarWinds' monitoring platform. A monitoring platform is the control-room screen for a network: it polls devices and servers, collects their health and performance, and shows engineers what is up, what is down, and what is struggling — all in one place. To do that job, Orion is normally given broad reach. CISA puts the consequence plainly: Orion is typically configured with pervasive, highly privileged accounts — accounts that are trusted widely across an organisation. Why this matters: a compromise of the monitoring server is not a compromise of one ordinary workstation. It can become a foothold anywhere those privileged accounts are trusted.

Orion was also central to the business. For the nine months ended September 30, 2020, SolarWinds reported Orion revenue of approximately $343 million, about 45 percent of total revenue. The product that carried the back door was not a side project. It was close to half the company.

The problem: the build itself was compromised

The setup has three parts, and each one defeats a defence people normally rely on.

First, the attack hit the build system, not the source code. SolarWinds' filing says the vulnerability was introduced as a result of a compromise of the Orion software build system and was not present in the source code repository. A build system is the factory line that turns source code into the installable software customers download. Reviewing the source code, however carefully, would not have shown this flaw — because the flaw was added after that stage, on the line itself.

Second, the finished update was properly signed. CISA says the adversary added a malicious version of the binary (a compiled program file) named solarwinds.orion.core.businesslayer.dll into the SolarWinds software lifecycle, and it was then signed by the legitimate SolarWinds code-signing certificate. Code signing is meant to answer the question "did this really come from the vendor, unaltered?" Here the honest answer to the first half was yes — and that is exactly why the check failed to protect anyone. The signature proved where the package came from. It could not prove the factory had not been broken into.

Third, the back door behaved like the product. Once installed, CISA says, the malicious binary calls out to a victim-specific avsvmcloud[.]com domain using a protocol designed to mimic legitimate SolarWinds protocol traffic. (The brackets are how security advisories print a dangerous address so nobody clicks it by accident.) After that first check-in, the attacker could use the reply from the Domain Name System (DNS — the internet's address book) to selectively hand back new domains or addresses for interactive command and control (C2) — the channel through which an attacker gives a compromised machine its next instructions. In plain terms: the implant phoned home disguised as normal product chatter, and only chosen victims were handed the next address.

An analogy: imagine a bottled-water plant where someone tampers with the bottling line, not the spring. The water source tests clean. Every bottle leaves with the genuine factory seal. Customers who check the seal — the right check, normally — are reassured by the very thing that was compromised upstream. That is a supply-chain attack: you do not attack each customer. You attack the one supplier they all trust, once.

How a trusted update carried a back door SOURCE CODE SolarWinds filing: the flaw was NOT in the source code repository BUILD SYSTEM HIT Malicious DLL added in the software lifecycle per CISA AA20-352A SIGNED AND SHIPPED Signed with the legitimate SolarWinds certificate Customers install it THE SIGNATURE WAS REAL. THE FACTORY WAS NOT SAFE. Updates released March to June 2020 carried the vulnerability Checking the seal proves who shipped it. It does not prove the line was clean.

What this shows: the three steps from the two primary sources, in order. Clean source code, a compromised build, and a genuinely signed update — which is why the usual trust check did not save anyone.

What happened

All dates are as given in CISA Alert AA20-352A and SolarWinds' December 14, 2020 filing. Keep the two clocks separate as you read: the long, quiet clock of 2020, when the back door was delivered and compromises began, and the fast clock of December 13 to 15, when the response happened in public.

2020 to 2021 — the documented timeline March to June 2020 — poisoned updates released CISA: compromises began in at least March 2020 December 13, 2020 — customers told; agencies ordered to disconnect About 33,000 Orion customers notified; CISA Emergency Directive 21-01 issued December 14, 2020 — SolarWinds files with the SEC Fewer than 18,000 may have had an installation containing the vulnerability December 15, 2020 — the beacon domain is blocked avsvmcloud[.]com resolves to a Microsoft blocklist address, per CISA December 17, 2020 — CISA publishes Alert AA20-352A Updated repeatedly; affected-version list updated January 6, 2021 April 15, 2021 — attribution The U.S. Government attributes the activity to the Russian SVR

What this shows: the whole case on one line — months of quiet delivery in 2020, then three public days in December, then attribution four months later.

March to June 2020 — the Relevant Period. That is SolarWinds' own name in its filing for the window when the affected updates were released. Products downloaded, implemented, or updated in that window contained the vulnerability, the filing says; products installed before it and never updated in it did not, and products installed after it did not. CISA, for its part, says it is aware of compromises of U.S. government agencies, critical infrastructure entities, and private sector organisations by an advanced persistent threat (APT) actor — a patient, well-resourced attacker — beginning in at least March 2020. CISA describes an actor that demonstrated patience, operational security, and complex tradecraft, and warns from the start that removing it would be highly complex and challenging.

The affected versions. In its January 6, 2021 update, CISA lists the Orion versions sharing the compromised DLL: 2019.4 HF5 (2019.4.5200.9083), 2020.2 RC1, 2020.2 RC2, 2020.2, and 2020.2 HF1. This page uses CISA's list, as labelled there. If your version is not on it, that alone is not an all-clear — see the other-routes point below.

December 13, 2020 — two moves on one day. SolarWinds delivered its communication to approximately 33,000 Orion customers who were active maintenance customers during and after the Relevant Period, with mitigation steps and a hotfix (a quick, targeted software fix) addressing the vulnerability in part; a second hotfix was expected on or before December 15. The same day, CISA issued Emergency Directive 21-01, ordering federal civilian agencies to disconnect affected devices. Disconnect first is a deliberate choice: it stops the known channel while investigators work out how far the actor has already gone inside.

December 14, 2020 — the filing. SolarWinds' Form 8-K puts the company's own early account on the public record: a highly sophisticated, targeted and manual supply-chain attack by an outside nation state, as it had been advised — with the careful note that SolarWinds had not independently verified the identity of the attacker. It also discloses a second thread: an attack vector used to compromise the company's own Microsoft Office 365 email, investigated with Microsoft, with no evidence found at that time that customer, personnel, or other data had been taken that way. Investigations, the filing stresses, were preliminary and ongoing.

The phone-home: disguised, selective, and patient ORION SERVER Back door installed avsvmcloud[.]com Traffic mimics the product DNS REPLY Selects victims CHOSEN VICTIMS GET A NEW C2 ADDRESS Most installs are left alone — delivery is not targeting The moving dashed lines are the disguised check-in. Selectivity is what made this espionage, not vandalism.

What this shows: how the back door worked after installation, in CISA's description — a disguised first call, then a DNS reply that could move only chosen victims on to interactive control.

December 15, 2020 — the beacon goes dark, with a warning attached. CISA reports that, through coordinated action by private-sector partners, avsvmcloud[.]com now resolved to 20.140.0[.]1, an address on the Microsoft blocklist. That negated future use of the implants. CISA immediately adds the limit: where the attacker had already moved control past the initial beacon, infection would likely continue despite the block. Cutting the phone line helps everyone who had not yet been called. It does not evict anyone already inside the house.

What follow-on looked like. For the victims the actor did choose, CISA documents identity attacks rather than noisy break-ins. One method: use escalated Active Directory privileges to compromise the SAML signing certificate. SAML is the system that lets one trusted login vouch for you to other services; whoever holds its signing key can create unauthorised but valid tokens — passes that services accept as genuine — and use them to reach hosted resources such as email. CISA also observed the actor adding tokens and certificates to existing Azure and Microsoft 365 service principals (the identities applications use), giving persistence that could interact with the cloud tenant while generating little evidence, and Microsoft reported new federation trusts added to on-premises infrastructure, where authentication could happen outside the owner's known systems. CISA further notes the actor targeted email accounts of key personnel, including IT and incident-response staff — the people who would run the cleanup.

The other doors. CISA is careful, and this page follows it: there were initial access routes other than Orion. CISA cites evidence of legitimate-account abuse, password guessing and password spraying, inappropriately secured administrative credentials reachable through remote access, and SAML-token abuse in incidents where no impacted SolarWinds instance was identified. Do not read this case as "every victim came through Orion." Some did not — which is why version-checking alone was never a sufficient response.

April 15, 2021 — attribution. Only in this update does CISA record that the U.S. Government attributes this activity to the Russian Foreign Intelligence Service (SVR). The December alert had not attributed it, and SolarWinds' December filing had not verified an identity. The four-month gap is part of the record: response had to happen long before attribution could.

The damage

The primary sources measure this damage in reach and risk, not in a single dollar total — and this page follows them rather than borrowing totals from elsewhere.

Reach, in three numbers that must not be merged. Over 300,000 customers in total. Approximately 33,000 Orion customers notified — that is the mailing list, not the casualty list. Fewer than 18,000 who may have had an installation containing the vulnerability — SolarWinds' own estimate, in its filing's careful wording. And inside that last group, CISA adds the distinction that matters most: not all organisations that had the back door delivered were targeted with follow-on actions. Delivery, installation, and exploitation are three different events. Any account that collapses them into one number is overstating what the sources say.

Risk, in CISA's own grading. CISA determined the threat posed a grave risk to the Federal Government, to state, local, tribal, and territorial governments, to critical infrastructure entities, and to other private sector organisations. That grading follows from position, not just count: a monitoring platform with pervasive privileged accounts, inside that many sensitive networks, holding a working back door for months, is a grave risk even before any single follow-on theft is proved.

Duration and difficulty. Compromises began in at least March 2020; public response began December 13. That is roughly nine months in which the actor — patient, by CISA's account — could choose its targets at leisure. And the exit was priced honestly from day one: CISA expected removing the actor from compromised environments to be highly complex and challenging. Forged-but-valid tokens, added cloud credentials, and new federation trusts do not disappear when you uninstall one product. Each is a separate lock the attacker copied a key for, and each has to be found and changed.

What the sources do not do is name the follow-on victims on this page's authority, or total the losses. SolarWinds' filing says plainly that at that time it was unable to predict the financial, legal, or reputational consequences. This page keeps that honesty: the documented damage is the scale of delivery, the position of the compromised product, the identity tradecraft used against chosen victims, and a cleanup CISA warned would be long and hard.

How they recovered

Step one: tell every Orion customer, not just the known-affected. On December 13, SolarWinds wrote to all approximately 33,000 active maintenance Orion customers from the Relevant Period onward — a wider net than its fewer-than-18,000 estimate — with mitigation steps and a first hotfix addressing the vulnerability in part. A second hotfix followed, expected on or before December 15. Telling the wider group first, and refining later, is the right order when the cost of a missed customer is an undetected back door.

Step two: disconnect, by emergency order. CISA's Emergency Directive 21-01, also December 13, ordered federal civilian agencies to disconnect affected devices, with supplemental guidance following, most recently January 6, 2021 at the time of that update. For everyone else, the directive was still the clearest public signal of the expected posture: isolate the monitoring platform first; investigate from safety, not while it is still connected and privileged.

Step three: kill the beacon. By December 15, the avsvmcloud[.]com domain resolved to a Microsoft blocklist address, ending future use of the implants' first call-home — with CISA's stated caveat that infections already moved past that beacon would likely continue.

Step four: hunt the identity layer, with a tool built for it. Because follow-on abuse lived in tokens, certificates, and cloud application identities, CISA built and published Sparrow.ps1 to help detect possibly compromised accounts and applications in Azure and Microsoft 365 environments. CISA is modest about it — it covers a narrow scope and is neither comprehensive nor exhaustive — and that modesty is itself the lesson: there was no single sweep that could declare an environment clean.

Step five: keep the record updated, including attribution. Alert AA20-352A was revised repeatedly — through December 2020, January and February 2021, and finally April 15, 2021, when it carried the U.S. Government's attribution to the Russian SVR. Recovery here includes the public record itself: responders in month four were working from a better map than responders in week one, because the alert kept moving.

The fix: technology and controls that came out of it

No single patch fixes a supply-chain compromise, because the failure was in trust, not in one line of code. The controls this case points to — drawn from what CISA directed and documented — work as a set.

Protect the build like production, because it is production. SolarWinds' filing locates the insertion in the build system, outside the source repository. The control that follows is direct: treat build servers, signing keys, and release pipelines as your most sensitive systems — isolated, access-logged, and verified — and compare what the build produced against what the source should have produced. A difference between the reviewed code and the shipped binary is a finding, not a curiosity.

Do not let a signature end the conversation. The update was legitimately signed. Signing still matters — it stops crude tampering — but this case is the standing proof that it cannot be the only check on vendor software. Organisations need their own layers behind it: staging vendor updates, watching what changed in behaviour after an update, and monitoring even trusted, signed software for traffic it has never made before — such as a monitoring server suddenly resolving unusual external domains.

Shrink what monitoring can reach. CISA's warning about pervasive privileged accounts is the network-design lesson. A monitoring platform needs broad visibility; it does not follow that its accounts must be trusted everywhere, forever, with no segmentation (separation that limits how far an intruder can move). Least privilege — giving each system only the access its job requires — plus segmentation between the monitoring tier and the crown jewels, is what turns "the watcher is compromised" from a catastrophe into a contained incident.

Defend the identity layer as a first-class surface. The follow-on tradecraft was about tokens and trust: SAML signing certificates, added service-principal credentials, new federation trusts. The fixes are correspondingly specific — protect signing keys like signing keys, alert on any new credential added to a cloud application or any new federation trust, and hunt for the token anomalies CISA lists, such as unusually long token lifetimes or tokens with no matching login. An attacker who can mint valid passes does not need to break doors at all.

Plan for the supplier incident, not just your own. Emergency Directive 21-01 worked as a template even outside government: a pre-written answer to "what do we disconnect, in what order, on whose say-so, when a trusted vendor tells us its update was poisoned?" Organisations that had an inventory of where Orion — or any privileged platform — sat, and what its accounts could reach, could act on December 13. Organisations that first had to go and find their monitoring servers lost the days that mattered.

What this means for you

Enterprise network engineers

Your Orion is every privileged platform you run: the network management system, the backup server, the software-deployment tool — anything with accounts trusted across the estate and a vendor update channel into the middle of your network. Three habits fall out of this case. Keep a live inventory of those platforms, their versions, and what their accounts can reach, so a vendor notice becomes a checklist instead of a treasure hunt. Stage and watch vendor updates even when they are signed — especially then, because signed is what your users will cite to skip the staging. And rehearse the disconnect decision: who can order a core platform isolated, out of hours, on a vendor's say-so? If the answer needs a meeting, December 13 is what that delay costs.

Hyperscaler engineers

You are the supplier in this story, at far larger scale: your build pipelines and signing infrastructure are the single point whose compromise becomes everyone's incident. SolarWinds' filing should be read as a pipeline threat model — the flaw was absent from source and present in the shipped binary, so source review, however strong, was looking at the wrong artefact. Verify the artefact: reproducible builds, build-to-source comparison, signing keys in hardened, audited custody, and release processes where no single compromised stage can both alter the product and bless it. Then assume a customer will one day have to disconnect you on a Sunday: version transparency, precise affected-version lists like CISA's January 6 update, and fast, honest filings are what make that day survivable for both sides.

HFT / low-latency engineers

Your supply chain is market data, execution gateways, and the vendor libraries inside your fastest code — systems you trust at microsecond scale and patch reluctantly because change itself feels like risk. This case is the counterweight: the March-to-June window shows what unpatched-by-choice becomes when the flaw arrives through the trusted channel itself. The controls that map are provenance and blast radius: know exactly which vendor builds are running where, pin and record them, monitor even your most trusted processes for any external connection they have no business making, and keep a rehearsed way to pull a vendor component out of the path without rebuilding the strategy around it. In your world as in SolarWinds' customers', the seal on the bottle is not a monitoring strategy.

Try it yourself

Two free Packet Path tools build the habits this case rewards. Start with the Config to Topology Mapper: paste device configurations and it draws the network they actually describe and surfaces mismatches — the inventory habit, practised. Knowing exactly where your privileged platforms sit and what they connect to is what turns a vendor emergency notice into an afternoon of checks instead of a week of discovery. Then use the Network Config Verifier to compare configurations side by side and flag inconsistencies: the build-to-source comparison instinct, at network scale. SolarWinds' lesson is that the artefact you run is the only one that counts — check the thing itself, not the paperwork about it.

Sources

Primary source — U.S. Cybersecurity and Infrastructure Security Agency (CISA), Alert AA20-352A: Advanced Persistent Threat Compromise of Government Agencies, Critical Infrastructure, and Private Sector Organizations (originally published December 17, 2020; last revised April 15, 2021). Facts taken from this alert include: compromises beginning in at least March 2020 and the grave-risk determination; the malicious solarwinds.orion.core.businesslayer.dll added in the software lifecycle and signed by the legitimate SolarWinds code-signing certificate; the victim-specific avsvmcloud[.]com call-out mimicking legitimate traffic and the DNS-based selection of C2; the affected-version list as updated January 6, 2021 (2019.4 HF5, 2020.2 RC1, 2020.2 RC2, 2020.2, 2020.2 HF1); Emergency Directive 21-01 of December 13, 2020; the December 15, 2020 resolution of avsvmcloud[.]com to the Microsoft blocklist address 20.140.0[.]1 and its stated limit; the statements that not all backdoored organisations were targeted and that other initial-access vectors existed; the SAML, Azure/Microsoft 365, and federation-trust tradecraft; Sparrow.ps1; and the April 15, 2021 U.S. Government attribution to the Russian Foreign Intelligence Service (SVR). Full text: https://www.cisa.gov/news-events/cybersecurity-advisories/aa20-352a

Primary source — SolarWinds Corporation, Form 8-K, Current Report (December 14, 2020), Item 8.01, filed with the U.S. Securities and Exchange Commission. Facts taken from this filing include: the vulnerability inserted in Orion updates released between March and June 2020 (the Relevant Period), introduced through a compromise of the Orion software build system and not present in the source code repository; the December 13, 2020 communication to approximately 33,000 Orion customers; the belief that fewer than 18,000 may have had an installation containing the vulnerability; over 300,000 customers in total; Orion revenue of approximately $343 million (about 45 percent of total revenue) for the nine months ended September 30, 2020; the hotfix and expected second hotfix; the separate Microsoft Office 365 email compromise investigation with no evidence of exfiltration found at that time; and the statement that financial, legal, or reputational consequences could not yet be predicted. Full text: https://www.sec.gov/Archives/edgar/data/1739942/000162828020017451/swi-20201214.htm

No other sources are used for facts on this page. Where the two primaries differ in emphasis — CISA on mechanism and tradecraft, the filing on customer counts and company impact — each figure is attributed to its own source in the text, and the fewer-than-18,000 figure is presented throughout as what the filing says it is: an estimate of installations that may have contained the vulnerability, not a count of confirmed follow-on victims.

Key takeaways

Keep reading