Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
MalwareUsed by 5 actors

SUNBURST

Also known asSolorigate

SUNBURST is a trojanized DLL backdoor inserted into SolarWinds Orion software updates as part of the 2020 SolarWinds supply-chain compromise. It was integrated into the Orion update framework after attackers compromised SolarWinds’ development/build environment and infected Orion source code; the malicious builds were digitally signed by SolarWinds and distributed to customers between approximately March and June 2020. The malware is also referred to as Solorigate, but SUNBURST is the most widely used name in the provided reporting.

The malware provided remote access and command-and-control capability in victim environments and was used as an initial foothold for follow-on intrusion activity. It communicated with third-party command-and-control infrastructure over HTTP using GET and POST requests, used Base64 encoding in its C2 traffic, and generated runtime C2 traffic to subdomains of avsvmcloud[.]com. FireEye reported a killswitch associated with avsvmcloud[.]com that could cause SUNBURST to terminate under certain conditions, though this did not remove threat actors from networks where additional persistence had already been established.

SUNBURST was designed for stealth and selective execution. Reporting states it delayed execution for roughly 12 to 14 days, would not execute unless the host was joined to a domain, and would not execute if its C2 domain resolved to a private IP address. It performed extensive environment checks for analysis and security tooling, including process, service, and driver blacklist checks using hardcoded hashed values. It queried WMI with "Select * From Win32_SystemDriver" to retrieve driver listings, and attempted to disable software security services after checking a hardcoded FNV-1a + XOR hashed blocklist. It also removed HTTP proxy registry values to clean up traces of execution.

Observed host reconnaissance included collecting the username from compromised hosts and reading HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\MachineGuid. The malware’s execution chain included a named pipe, 583da945-62af-10e8-4902-a8f205c72b2e, after its dormant period. A weaponized Orion DLL could be identified by an injected OrionImprovementBusinessLayer class in the SolarWinds.Orion.Core.BusinessLayer namespace.

SUNBURST is associated in the provided content with the SolarWinds compromise and with the threat actor tracked as UNC2452 by FireEye and later named NOBELIUM by Microsoft; public reporting also linked the campaign to APT29/Cozy Bear/Russian SVR. The malware was used against public- and private-sector victims globally, including government, consulting, technology, telecom, and extractive organizations, with reporting noting major impact across U.S. government agencies and other high-value targets. The content also states SUNBURST had capability to deliver the memory-only dropper TEARDROP, which was observed delivering Cobalt Strike Beacon and other malware.

Share:
For your environment

Hunt this family in your stack

Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.

THREAT ACTORS

Groups observed using it

5 distinct threat actors attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details
APT28

Attackers will be retooling, so don’t anticipate finding specifics for SUNBURST malware.

via sans blogsans.org
SVR

The threat actor inserted malicious software into Solarwinds’ development environment, infecting Orion’s source code with the SUNBURST malware. The compromised build was pushed to customers as an update to their existing Orion installations, deploying SUNBURST into customer environments.

via ca ccscyber.gc.ca
APT29

The threat actor inserted malicious software into Solarwinds’ development environment, infecting Orion’s source code with the SUNBURST malware. The compromised build was pushed to customers as an update to their existing Orion installations, deploying SUNBURST into customer environments.

via ca ccscyber.gc.ca
Dark Halo

the company's software by inserting the Sunburst malware into some updates for the SolarWinds Orion app

via zdnet zero dayzdnet.com
Turla

A second one is the Sunburst (Solorigate) backdoor malware deployed by the SolarWinds hackers on the systems of organizations who installed trojanized Orion builds via the platform's built-in automatic update mechanism.

via bleeping computerbleepingcomputer.com
MITRE ATT&CK

Techniques & procedures

32 distinct techniques documented for this family, organized by ATT&CK tactic.

Initial Access

5 techniques
T1195Supply Chain CompromiseEvidence4

Supply chain attacks are not common and the SolarWinds Supply-Chain Attack is one of the most potentially damaging attacks we’ve seen in recent memory.

T1195.001Compromise Software Dependencies and Development ToolsEvidence1

In this case, they were actually deploying it through SolarWinds own distribution channels.

T1195.002Compromise Software Supply ChainEvidence2

Use of malicious SolarWinds update : Inserting malicious code into legitimate software updates for the Orion software that allow an attacker remote access into the victim’s environment

T1195.003Compromise Hardware Supply ChainEvidence1

State-sponsored threat actors have demonstrated their ability to compromise service providers such as MSPs as a method of infiltrating the supply chain of organizations of strategic interest, establishing persistence, and securing access to downstream targets.

T1199Trusted RelationshipEvidence1

Malwarebytes said its intrusion is not related to the SolarWinds supply chain incident since the company doesn't use any of SolarWinds software in its internal network.

Execution

4 techniques
T1047Windows Management InstrumentationEvidence1

The content repeatedly describes threat actors and malware using WMI/WMIC/wmiexec for remote execution, lateral movement, discovery, persistence, and administrative actions; e.g., 'APT41 used WMI in several ways, including for execution of commands via WMIEXEC as well as for persistence via PowerSploit' and 'Scattered Spider used Windows Management Instrumentation (WMI) to move laterally via Impacket.'

T1059Command and Scripting InterpreterEvidence1

'After taking control of the Orion update mechanism, the attackers were using it to install a backdoor that FireEye researchers are calling Sunburst.'

T1127Trusted Developer Utilities Proxy ExecutionEvidence1

SolarWinds has published limited information in which they state they believe the build environment was compromised.

T1574.012COR_PROFILEREvidence1

SUNBURST deleted previously-created Image File Execution Options (IFEO) Debugger registry values.

Persistence

2 techniques
T1112Modify RegistryEvidence3

Neoichor can clear the browser history on a compromised host by changing the ClearBrowsingHistoryOnExit value to 1 in the HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Privacy Registry key.

T1546Event Triggered ExecutionEvidence1

If further actions were taken, TEARDROP or RAINDROP backdoors would be deployed, which would install a customized Cobalt Strike beacon in the environment.

Privilege Escalation

1 technique
T1546Event Triggered ExecutionEvidence1

If further actions were taken, TEARDROP or RAINDROP backdoors would be deployed, which would install a customized Cobalt Strike beacon in the environment.

Stealth

11 techniques
T1027Obfuscated Files or InformationEvidence1

The content repeatedly describes malware and threat actors using obfuscated code, encrypted strings, Base64/XOR/RC4/AES encoding, VMProtect/ConfuserEx/SmartAssembly, stack strings, control-flow flattening, opaque predicates, and hidden payloads to evade analysis and detection.

T1036MasqueradingEvidence1

During the 2016 Ukraine Electric Power Attack, DLLs and EXEs with filenames associated with common electric power sector protocols were used to masquerade files.

T1036.004Masquerade Task or ServiceEvidence1

RedCurl mimicked legitimate file names and scheduled tasks, e.g. MicrosoftCurrentupdatesCheck and MdMMaintenenceTask to mask malicious files and scheduled tasks.

T1070Indicator RemovalEvidence3

Bisonal has deleted Registry keys to clean up its prior activity. FIN8 has deleted Registry keys during post compromise cleanup activities. SUNBURST also deleted previously-created Image File Execution Options (IFEO) Debugger registry values and registry keys related to HTTP proxy to clean up traces of its activity.

T1070.004File DeletionEvidence3

The content repeatedly describes threat actors and malware deleting files, tools, scripts, logs, droppers, staged data, and artifacts from compromised systems to cover tracks, remove evidence, or self-delete.

T1070.009Clear PersistenceEvidence1

CSPY Downloader has the ability to remove values it writes to the Registry.

T1127Trusted Developer Utilities Proxy ExecutionEvidence1

SolarWinds has published limited information in which they state they believe the build environment was compromised.

T1497Virtualization/Sandbox EvasionEvidence1

This effectively prevents the use of malware sandboxes or other instrumented environments to detect it.

T1497.001System ChecksEvidence2

unless the machine is joined to a domain, the malware will not execute.

T1497.003Time Based ChecksEvidence1

the malware checks file system timestamps to ensure the product has been deployed for 12-14 days before it does its first beacon.

T1574.012COR_PROFILEREvidence1

SUNBURST deleted previously-created Image File Execution Options (IFEO) Debugger registry values.

Defense Impairment

1 technique
T1112Modify RegistryEvidence3

Neoichor can clear the browser history on a compromised host by changing the ClearBrowsingHistoryOnExit value to 1 in the HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Privacy Registry key.

Discovery

9 techniques
T1012Query RegistryEvidence1

The content repeatedly describes malware and threat actors querying, enumerating, searching, reading, or checking Windows Registry keys and values, e.g., "ADVSTORESHELL can enumerate registry keys," "APT41 queried registry values to determine items such as configured RDP ports and network configurations," and "Reg may be used to gather details from the Windows Registry of a local or remote system at the command-line interface."

T1016System Network Configuration DiscoveryEvidence1

The content repeatedly describes malware and threat actors using commands and APIs such as ipconfig /all, ifconfig, arp -a, route print, nbtstat, netsh, GetAdaptersInfo, and GetIpNetTable to gather IP addresses, MAC addresses, DNS, DHCP, gateways, routing tables, ARP cache, proxy settings, domains, and network adapter/interface details.

T1033System Owner/User DiscoveryEvidence1

The content repeatedly describes malware and threat actors collecting usernames, identifying logged-in users, running whoami/query user/quser, checking whether the current user is an administrator, enumerating user sessions, and gathering account details from compromised hosts.

T1057Process DiscoveryEvidence1

The content repeatedly describes malware and threat actors obtaining lists of running processes, using utilities such as tasklist, ps, WMI, Get-Process, CreateToolhelp32Snapshot, EnumProcesses, and similar APIs/commands to enumerate active processes on victim systems.

T1082System Information DiscoveryEvidence2

SUNBURST then communicated with the threat actors, who would verify that the accessed environment had information of value worth exfiltrating.

T1083File and Directory DiscoveryEvidence1

The content repeatedly describes malware and threat actors listing files and directories, enumerating drives, searching for files by extension/name/path, retrieving file metadata, and browsing file systems (for example: "APT28 has used Forfiles to locate PDF, Excel, and Word documents during collection" and "cmd can be used to find files and directories with native functionality such as dir commands").

T1497Virtualization/Sandbox EvasionEvidence1

This effectively prevents the use of malware sandboxes or other instrumented environments to detect it.

T1497.001System ChecksEvidence2

unless the machine is joined to a domain, the malware will not execute.

T1497.003Time Based ChecksEvidence1

the malware checks file system timestamps to ensure the product has been deployed for 12-14 days before it does its first beacon.

Collection

1 technique
T1005Data from Local SystemEvidence2

The content repeatedly describes threat actors and malware collecting, stealing, identifying, copying, or staging files, documents, credentials, logs, databases, and other information from compromised hosts or local systems.

Command and Control

4 techniques
T1071Application Layer ProtocolEvidence2

used by the SolarWinds hackers to communicate with systems compromised by the backdoored Orion product updates | a key domain name — avsvmcloud[.]com — that was used by the SolarWinds hackers to communicate with systems compromised by the backdoored Orion product updates

T1071.001Web ProtocolsEvidence3

The content repeatedly describes threat actors and malware using HTTP and HTTPS for command and control, such as: "Sandworm Team used BlackEnergy to communicate between compromised hosts and their command-and-control servers via HTTP post requests."

T1132Data EncodingEvidence2

C2 traffic from ADVSTORESHELL is encrypted, then encoded with Base64 encoding... APT19 HTTP malware variant used Base64 to encode communications to the C2 server... APT33 has used base64 to encode command and control traffic.

T1568.002Domain Generation AlgorithmsEvidence1

FireEye has released domains useful for hunting... the attacker is absolutely trying to segregate their initial stage from their ongoing stages

Other

1 technique
T1562Impair DefensesEvidence2

The content repeatedly describes threat actors and malware disabling, stopping, uninstalling, or modifying antivirus, EDR, Windows Defender, AMSI, logging, and other security controls.

INDICATORS OF COMPROMISE

IOCs tracked for this family

143 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.

View more in app
Network
89 tracked

IPs, domains, and DNS infrastructure linked to this family.

Hashes
49 tracked

File hashes (MD5, SHA-1, SHA-256) from samples and reports.

Other
5 tracked

Other indicator types observed in public reporting.

TypeValueLatest sighting
domain●●●●●●●●●●●●View more in app22 days ago
hash.sha256●●●●●●●●●●●●View more in app2 years ago
hash.sha256●●●●●●●●●●●●View more in app2 years ago
hash.sha256●●●●●●●●●●●●View more in app2 years ago
hash.sha256●●●●●●●●●●●●View more in app2 years ago
hash.sha256●●●●●●●●●●●●View more in app2 years ago
ACTIVITY FEED

Recent activity

119 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching143

Match every observed IP, domain, and hash against your live telemetry.

Threat actor attribution5

Named campaigns wielding this family, with evidence pinned to each claim.

Exploited vulnerabilities

CVEs this family uses for access and lateral movement.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

MITRE ATT&CK mapping32

Every documented technique, ranked by evidence weight.

Researcher chatter

Reddit, Mastodon, and CTI community discussion around this family.