INTELLIGENCEReference · public sources
← Incidents

Incident reportSupply chain compromiseReport version 1 · November 21, 2026

SolarWinds Orion supply chain compromise (SUNBURST)

Trojanized SolarWinds Orion software updates gave an intrusion set access to downstream networks. Mandiant disclosed the campaign in December 2020; the UK and US governments attributed it to Russia's SVR in April 2021.

CorroboratedAttribution: SVR (APT29)Reference data · public sources

01Executive assessment

  • CorroboratedAttackers trojanized SolarWinds Orion business software updates to distribute malware. [1]
  • CorroboratedThe trojanized updates were signed from March to May 2020 and posted to the SolarWinds update site. [1]
  • CorroboratedVictims included government, consulting, technology, telecom and extractive entities in North America, Europe, Asia and the Middle East. [1]

Implication: organizations in the affected sectors should confirm whether the access paths described in the sources apply to their own environment. A matching sector or technology is a reason to examine exposure, not evidence of compromise.

02What happened

Trojanized SolarWinds Orion software updates gave an intrusion set access to downstream networks. Mandiant disclosed the campaign in December 2020; the UK and US governments attributed it to Russia's SVR in April 2021.

Incident type
Supply chain compromise
Event period
March 2020 to May 2020
Date precision
month
Evidence basis
Original researcher disclosure plus government attribution
Sectors
Government, Consulting, Technology, Telecommunications, Extractive industries

Trojanized updates signed and posted March to May 2020; campaign may have begun as early as spring 2020.

03Evidence chronology

Publication dateDevelopmentTypeSource
December 13, 2020Mandiant (FireEye) discloses the SUNBURST supply chain campaign under UNC2452.Researcher disclosure[1]
April 15, 2021UK and US governments attribute the compromise to the SVR.Government attribution[2]
April 27, 2022Mandiant merges UNC2452 into APT29.Analytical reassessment[3]

Event dates, source publication dates and our observation time (November 21, 2026) are recorded separately. Observation time is when DarkFire first collected the record, not when the activity occurred.

04Targets and geography

TargetRoleLocationPrecision and basis
SolarWindsCompromised software supplier (named by source)Austin, Texas, United Statescity · Organization headquarters, affected system location unspecified

Regions named by the source: North America, Europe, Asia, Middle East. Regional scope is shown in the list, not as map points.

Locations describe affected organizations or countries as stated by the sources. They never indicate where an attacker operates from.

05Attribution assessment

Attributed actor
SVR (APT29)
Assessed by
UK National Cyber Security Centre (with the US government)
Confidence
highly likely (as stated by source)
Sources
[2][3]

DarkFire aggregates attribution published by the named assessing organization; it does not make its own attribution. Event evidence, actor attribution and location precision are separate judgments.

06Technical behavior

ATT&CKTechnique
T1195.002Compromise Software Supply Chain

Techniques listed here are the behaviors described for this incident, not the actor's full ATT&CK catalog.

EVIDENCEACTOR AND TECHNIQUESMandiant (formerly FireEye) v…December 13, 2020UK National Cyber Security Ce…April 15, 2021Mandiant via Google CloudApril 27, 2022APT29 / Cozy BearUK National Cyber Security Centre…Compromise Software Supply Ch…T1195.002SolarWinds

07Software and indicators

No publicly shareable indicators are recorded for this incident.

08Business exposure and priorities

Organizations in government, consulting, technology, telecommunications should review whether they share the conditions described in the sources: the same technology, supplier relationships or access paths. Relevance is a reason to examine exposure, not a finding of compromise.

The APT29 dossier sets out defender priorities for this actor's documented behaviors.

09Defensive actions

Inventory non-production tenants, dormant accounts and application identities alongside production users. Assign an owner and business purpose to each, remove access that is no longer required and examine high-privilege grants. Review device enrollment and session policies. These actions address the types of identity exposure described in the joint cloud advisory; implementation should account for the organization's actual services and authentication design.

Inspect supplier and application trust. Identify which providers can administer accounts, read mail or distribute software, and determine what evidence would reveal misuse. Retain identity and mail audit events in a form investigators can correlate across accounts and applications. During a suspected intrusion, evaluate consent grants, credentials, sessions and persistence together. A password reset addresses one mechanism and should not be treated as evidence that every access path has been removed.

From the APT29 dossier. For each action, name a control owner, the supporting evidence and a completion criterion.

10Analytic gaps

  • Whether access persists at any affected organization is unknown unless newer evidence is published.

11Source notes and changes

  1. [1]Highly Evasive Attacker Leverages SolarWinds Supply Chain to Compromise Multiple Global Victims With SUNBURST BackdoorMandiant (formerly FireEye) via Google Cloud · published December 13, 2020 · updated 2022-05 · collected November 21, 2026
  2. [2]UK and US call out Russia for SolarWinds compromiseUK National Cyber Security Centre · published April 15, 2021 · collected November 21, 2026
  3. [3]Assembling the Russian Nesting Doll: UNC2452 Merged into APT29Mandiant via Google Cloud · published April 27, 2022 · collected November 21, 2026

Version 1, published November 21, 2026. No corrections recorded. Report an error to have it reviewed; corrections and retractions keep the previous version visible.