vendor binary

The SolarWinds Orion SUNBURST Backdoor

Updated 5 Oct 2026 · Incident date 24 Mar 2020

SolarWinds Orion Platform 2019.4 HF5 shipped a signed file carrying the SUNBURST backdoor from March 2020.

The backdoor sat in SolarWinds.Orion.Core.BusinessLayer.dll. It waited 12 to 14 days, then contacted a server and ran commands.

Major incident. SolarWinds received $50 million in insurance proceeds during 2022 and 2023 for its 2020 cyberattack. This excludes customer losses. Impact source

What happened

Attackers inserted code into the Orion build process. SolarWinds signed the DLL and sent it in a normal update package.

  • The backdoor runs only inside solarwinds.businesslayerhost processes.
  • It stays dormant for a random period of 12 to 14 days.
  • It does not run when it finds security or forensic tools.
  • It builds a unique subdomain of avsvmcloud.com for each victim.
  • Its traffic imitates the Orion Improvement Program.

The bad updates went out from March to May 2020.

Affected versions

  • Orion Platform builds from 2019.4 HF5 through 2020.2.1, before the fix.
  • 2019.4 HF4: clean baseline before the bad update.
  • 2019.4 HF5 (build 2019.4.5220.20574): first trojanized build, signed 24 March 2020.
  • 2020.2.1 HF1: the release that Mandiant says to upgrade to, after you save forensic data.

Indicators of compromise

  • SolarWinds.Orion.Core.BusinessLayer.dll MD5: b91ce2fa41029f6955bff20079468448.
  • Update package CORE-2019.4.5220.20574-SolarWinds-Core-v2019.4.5220-Hotfix5.msp MD5: 02af7cec58b9a5da1c542b5a32151ba1.
  • Command domain: avsvmcloud.com and its subdomains, including regional appsync-api names.
  • Signing certificate serial number: 0f:e9:73:75:20:22:a6:06:ad:f2:a3:6e:34:5d:c0:ed.
  • File gracious_truth.jpg, read by the TEARDROP dropper.

How to check

Hash the DLL on every Orion server and compare it with the MD5 above.

Get-ChildItem -Path "C:\Program Files (x86)\SolarWinds" -Recurse -Filter SolarWinds.Orion.Core.BusinessLayer.dll | Get-FileHash -Algorithm MD5

Search DNS logs for the command domain.

Select-String -Path .\dns.log -Pattern "avsvmcloud"

What to do now

  1. Isolate Orion servers and block their internet egress.
  2. Save forensic images and logs. Then upgrade to Orion 2020.2.1 HF1 or later.
  3. Change the passwords of accounts that have access to the Orion servers.
  4. Run the Mandiant YARA rules from the sunburst_countermeasures repository on GitHub on affected hosts.

Frequently asked questions

Who is behind SUNBURST?

Mandiant tracks the actor as UNC2452.

What came after the backdoor?

Mandiant says the attackers used a memory-only dropper named TEARDROP and Cobalt Strike BEACON on selected victims.

Which Orion versions are bad?

Builds from 2019.4 HF5 (2019.4.5220.20574) through 2020.2.1, before the fix.

Sources

  1. cloud.google.com/blog/topics/threat-intelligence/evasive-attacker-leverages-solarwinds-supply-chain-compromises-with-sunburst-backdoor
  2. microsoft.com/en-us/security/blog/2020/12/18/analyzing-solorigate-the-compromised-dll-file-that-started-a-sophisticated-cyberattack-and-how-microsoft-defender-helps-protect/

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library