Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
MalwareRansomwareUsed by 7 actorsExploits 1 CVE

Darkside

DarkSide is a ransomware-as-a-service (RaaS) operation and ransomware family first publicly reported in 2020 and later described as defunct/retired in the provided reporting. It is best known for the May 2021 Colonial Pipeline incident, which the FBI confirmed was caused by DarkSide ransomware and attributed to a DarkSide affiliate. That intrusion disrupted Colonial Pipeline’s IT environment, led the company to shut down pipeline operations, caused fuel shortages and panic buying across parts of the U.S. East Coast, and resulted in a ransom payment of about 75 bitcoin (roughly $4.4 million at the time). The U.S. Department of Justice later seized approximately $2.3 million in cryptocurrency tied to that payment.

The content consistently describes DarkSide as a double-extortion RaaS program in which core operators supplied ransomware tooling, management infrastructure, and leak-site capabilities to affiliates in exchange for a share of ransom proceeds. Reported affiliate terms included revenue sharing tiers, an interview process for prospective affiliates, and administrative panels for building payloads, managing victims, and controlling publication of stolen data. DarkSide was associated with at least 60 known double-extortion cases in the referenced period and its leak site reportedly listed data from more than 80 victim organizations in the U.S. and Europe.

Observed intrusion patterns in the content include initial access via phished or stolen credentials, purchased VPN access, brute-force and password-spraying activity, phishing-delivered malware, and exploitation of SonicWall SMA100 vulnerability CVE-2021-20016 by at least one affiliate cluster. FireEye linked multiple affiliate clusters to the ecosystem, including UNC2628, UNC2659, and UNC2465. Reported tradecraft included use of legitimate corporate VPN credentials, TeamViewer for persistence, Smokedham .NET backdoor delivery, NGROK to expose remote desktop services, and use of commodity tooling such as Cobalt Strike and SystemBC.

DarkSide targeted both Windows and Linux systems. The Windows variant appended a unique extension to encrypted files, attempted privilege escalation via the CMSTPLUA technique when not already elevated, terminated services associated with backup and database products including Commvault, Veeam, MailEnable, and SQL Server, attempted to tamper with Sophos services, and deleted Volume Shadow Copies. The Linux variant was delivered as an ELF binary and specifically targeted VMware ESX/ESXi environments by encrypting VMDK virtual disk files, including under /vmfs/volumes/. The content also states DarkSide was one of a small number of ransomware strains at the time capable of encrypting VMware ESXi shared virtual hard drives.

In investigated incidents, dwell times ranged from roughly 44 to 88 days, with a reported median around 45 days in Sophos cases, although some affiliate activity moved from access to deployment much faster. During dwell time, actors conducted reconnaissance, lateral movement via PSExec, RDP, and SSH, and exfiltrated data from multiple departments. Stolen archives were uploaded to Mega or pCloud in reported cases.

DarkSide publicly claimed to be apolitical and profit-motivated, and said it would avoid certain sectors or public-interest targets, including healthcare and vaccine-related entities. However, the content notes that its affiliate model limited operator control over target selection and attack consequences. Multiple reports state DarkSide appeared to avoid targeting Russian, Kazakh, and Ukrainian organizations, and U.S. officials said there was evidence the actors were in Russia, though the provided content does not establish a confirmed nation-state link.

The malware and operation are associated in the content with affiliates and broader criminal ecosystems rather than a single state actor. Reporting also links DarkSide to the ELBRUS criminal group as the operator of the DarkSide RaaS ecosystem, and separate reporting states FIN7 managed DarkSide and BlackMatter as part of its own RaaS activity. The content further references cooperation or claimed association by criminal actors such as Wazawaka/Mikhail Matveev with DarkSide affiliates.

High-confidence indicators and notable artifacts directly mentioned in the content include use of CVE-2021-20016 against SonicWall SMA100 devices, CMSTPLUA privilege escalation, PSExec/RDP/SSH for lateral movement, TeamViewer persistence, Smokedham backdoor delivery, NGROK exposure of remote desktop services, Mega and pCloud for exfiltration, deletion of Volume Shadow Copies, termination of Commvault/Veeam/MailEnable/SQL Server services, and Linux targeting of VMDK files under /vmfs/volumes/ on VMware ESX/ESXi systems.

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.

EXPLOITED CVES

Vulnerabilities exploited

1 CVE Mallory has correlated with this family across public research and vendor advisories. Each row links to the full Mallory page for that vulnerability.

1 CVES
CVE-2021-20016SQL Injection in SonicWall SMA100 SSL VPNExploited in the wild

Since initially surfacing in August 2020, the creators of DARKSIDE ransomware and their affiliates have launched a global crime spree affecting organizations in more than 15 countries and multiple industry verticals. | The threat actor obtained initial access to their victim by exploiting CVE-2021-20016, an exploit in the SonicWall SMA100 SSL VPN product, which has been patched by SonicWall. There is some evidence to suggest the threat actor may have used the vulnerability to disable multi-factor authentication options on the SonicWall VPN, although this has not been confirmed.

via fireeyefireeye.com
THREAT ACTORS

Groups observed using it

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

View more details
FIN7

In 2023, FIN7 expanded its operations to include the deployment of ransomware through affiliations with RaaS groups such as REvil and Maze, while also managing its own RaaS programs, including the now-retired Darkside and BlackMatter.

via recorded future blogrecordedfuture.com
DEV-0289

ELBRUS developed their own RaaS ecosystem named DarkSide. They deployed DarkSide payloads as part of their operations and recruited and managed affiliates that deployed the DarkSide ransomware.

via microsoft generalmicrosoft.com
UNC2465

FireEye researchers documented five separate clusters of activity suspected of being connected to DarkSide, the Ransomware-as-a-Service (RaaS) network responsible for the Colonial Pipeline security incident.

via zdnet zero dayzdnet.com
UNC2628

FireEye researchers documented five separate clusters of activity suspected of being connected to DarkSide, the Ransomware-as-a-Service (RaaS) network responsible for the Colonial Pipeline security incident.

via zdnet zero dayzdnet.com
UNC2659

FireEye researchers documented five separate clusters of activity suspected of being connected to DarkSide, the Ransomware-as-a-Service (RaaS) network responsible for the Colonial Pipeline security incident.

via zdnet zero dayzdnet.com
DarkSide

The attack began when a hacker group identified as DarkSide accessed the Colonial Pipeline network. The attackers stole 100 gigabytes of data within a two-hour window. Following the data theft, the attackers infected the Colonial Pipeline IT network with ransomware that affected many computer systems, including billing and accounting.

via techtargettechtarget.com
MITRE ATT&CK

Techniques & procedures

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

Reconnaissance

1 technique
T1598Phishing for InformationEvidence1

In Sophos’ experience in data forensics and incident response to DarkSide attacks, the initial access to the target’s network came primarily as a result of phished credentials.

Resource Development

1 technique
T1583.006Web ServicesEvidence1

A person familiar with the matter said on Monday that the server also carried data from other DarkSide ransomware operations in progress...

Initial Access

2 techniques
T1078Valid AccountsEvidence1

In Sophos’ experience in data forensics and incident response to DarkSide attacks, the initial access to the target’s network came primarily as a result of phished credentials.

T1566PhishingEvidence1

UNC2465 now uses phishing emails to deliver DarkSide via the Smokedham .NET backdoor

Execution

2 techniques
T1059Command and Scripting InterpreterEvidence1

DarkSide follows generally the same tactics, techniques, and procedures of many other targeted ransomware campaigns — a mix of native Windows features, commodity malware... and off-the-shelf system and exploit tools...

T1574Hijack Execution FlowEvidence1

setting the registry value HKCU\Software\Classes\exefile\shell\open\command\Default to the malware path and executing slui.exe

Persistence

3 techniques
T1078Valid AccountsEvidence1

In Sophos’ experience in data forensics and incident response to DarkSide attacks, the initial access to the target’s network came primarily as a result of phished credentials.

T1112Modify RegistryEvidence1

It then writes out a Windows Registry key in HKEY_CLASSES_ROOT that associates files with the unique and peculiar file extension it has generated to that icon file...

T1543.003Windows ServiceEvidence1

via the creation of Windows services intended to launch BEACON. Notably, UNC2628 has repeatedly loaded BEACON with a service named ‘CitrixInit’

Privilege Escalation

4 techniques
T1068Exploitation for Privilege EscalationEvidence1

If it does not, the malware attempts to elevate its privileges using the CMSTPLUA technique.

T1078Valid AccountsEvidence1

In Sophos’ experience in data forensics and incident response to DarkSide attacks, the initial access to the target’s network came primarily as a result of phished credentials.

T1543.003Windows ServiceEvidence1

via the creation of Windows services intended to launch BEACON. Notably, UNC2628 has repeatedly loaded BEACON with a service named ‘CitrixInit’

T1548.002Bypass User Account ControlEvidence1

If the malware does not have elevated privileges, it attempts to perform one of two User Account Control (UAC) bypasses

Stealth

3 techniques
T1070.004File DeletionEvidence1

Like other ransomware, DarkSide also deletes Volume Shadow Copies, which could help recover some of the encrypted data if left unmolested.

T1078Valid AccountsEvidence1

In Sophos’ experience in data forensics and incident response to DarkSide attacks, the initial access to the target’s network came primarily as a result of phished credentials.

T1574Hijack Execution FlowEvidence1

setting the registry value HKCU\Software\Classes\exefile\shell\open\command\Default to the malware path and executing slui.exe

Defense Impairment

1 technique
T1112Modify RegistryEvidence1

It then writes out a Windows Registry key in HKEY_CLASSES_ROOT that associates files with the unique and peculiar file extension it has generated to that icon file...

Discovery

3 techniques
T1033System Owner/User DiscoveryEvidence1

The malware checks whether the Windows 10 user account under which it is running has administrative privileges...

T1082System Information DiscoveryEvidence1

DarkSide retrieves the target computer’s network adapter MAC address...

T1614System Location DiscoveryEvidence1

In the past few years, ransomware hackers have found an almost perfect solution — cryptocurrencies like Bitcoin. It's fast. It's easy. Best of all, it's largely anonymous and hard to trace.

Lateral Movement

4 techniques
T1021.001Remote Desktop ProtocolEvidence1

Using PSExec, Remote Desktop connections, and (in the case of Linux servers) SSH to move laterally within the network...

T1021.002SMB/Windows Admin SharesEvidence2

Using PSExec, Remote Desktop connections, and (in the case of Linux servers) SSH to move laterally within the network...

T1021.004SSHEvidence1

Using PSExec, Remote Desktop connections, and (in the case of Linux servers) SSH to move laterally within the network...

T1570Lateral Tool TransferEvidence1

Using PSExec, Remote Desktop connections, and (in the case of Linux servers) SSH to move laterally within the network...

Collection

1 technique
T1074Data StagedEvidence2

Using PSExec, Remote Desktop connections, and (in the case of Linux servers) SSH to move laterally within the network, the DarkSide actors uploaded archives of stolen files to the cloud storage providers Mega or pCloud in cases we’ve investigated.

Command and Control

2 techniques
T1071Application Layer ProtocolEvidence1

investigators managed to thwart at least some of the hackers' data theft by taking a cloud server offline.

T1105Ingress Tool TransferEvidence2

Loader feature: It can load a 2nd stage attack as EXE or DLL

Exfiltration

4 techniques
T1041Exfiltration Over C2 ChannelEvidence1

Wazawaka seems to have adopted the uniquely communitarian view that when organizations being held for ransom decline to cooperate or pay up, any data stolen from the victim should be published on the Russian cybercrime forums for all to plunder.

T1048Exfiltration Over Alternative ProtocolEvidence1

...the company did pay as it sought to retrieve the stolen information.

T1537Transfer Data to Cloud AccountEvidence2

Reuters on Sunday reported that investigators managed to thwart at least some of the hackers' data theft by taking a cloud server offline.

T1567.002Exfiltration to Cloud StorageEvidence1

Using PSExec, Remote Desktop connections, and (in the case of Linux servers) SSH to move laterally within the network, the DarkSide actors uploaded archives of stolen files to the cloud storage providers Mega or pCloud in cases we’ve investigated.

Impact

4 techniques
T1486Data Encrypted for ImpactEvidence13

DarkSide follows in the footsteps of double-extortion ransomware operators such as REvil, Maze, and LockBit—exfiltrating business data before encrypting it, and threatening public release if the victims don’t pay for a decryption key.

T1489Service StopEvidence3

We’ve observed them terminate the services relating to enterprise backup software from Commvault and Veeam, shut down the mail server software MailEnable, and kill SQL server database services, so they can encrypt any database they find.

T1490Inhibit System RecoveryEvidence1

Delete volume shadow copies

T1657Financial TheftEvidence2

This is known as a double-extortion tactic in which companies that refuse to pay for a decryption key are then threatened with the public leak of their files.

Other

2 techniques
T1562Impair DefensesEvidence1

The attackers... make an effort to terminate software that, if it was running, might otherwise interfere with the encryption process... They also attempt to uninstall or tamper with Sophos services if they’re present on the machine.

T1562.001Disable or Modify ToolsEvidence1

navigate to ESXi administration interfaces and disable snapshot features prior to the ransomware encryptor deployment

INDICATORS OF COMPROMISE

IOCs tracked for this family

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

View more in app
Network
13 tracked

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

Hashes
38 tracked

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

Other
11 tracked

Other indicator types observed in public reporting.

TypeValueLatest sighting
domain●●●●●●●●●●●●View more in app2 years ago
domain●●●●●●●●●●●●View more in app2 years ago
domain●●●●●●●●●●●●View more in app2 years ago
domain●●●●●●●●●●●●View more in app2 years ago
domain●●●●●●●●●●●●View more in app2 years ago
hash.md5●●●●●●●●●●●●View more in app2 years ago
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 matching62

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

Threat actor attribution7

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

Exploited vulnerabilities1

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 mapping31

Every documented technique, ranked by evidence weight.

Researcher chatter

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