Skip to main content
Mallory
← Back to News
ransomware-group-operationransomware-tooling-evolutionlateral-movement-methodinitial-access-method

DragonForce Ransomware Technical Analysis and Availability of a Decryptor

Threat Actor Intelligence · 2 sources · Updated 5mo ago · First seen Jan 15, 2026

DragonForce Ransomware Technical Analysis and Availability of a Decryptor

Security researchers published a technical breakdown of DragonForce ransomware, a ransomware operation that evolved from early underground forum activity into a broader ransomware-as-a-service (RaaS) model targeting both Windows and VMware ESXi environments. Reporting attributes DragonForce’s code lineage to leaked LockBit 3.0 and Conti code, with a custom build that heavily obfuscates strings and supports flexible encryption modes across local disks and network shares. Observed intrusion tradecraft includes initial access via exposed remote services (notably RDP), followed by lateral movement tooling such as Cobalt Strike and SystemBC, culminating in encryption of file servers and virtual machines and pressure via a dark web presence advertising stolen data.

S2W’s analysis describes DragonForce’s cryptography and operator options, including ChaCha8 for file encryption with RSA-4096 key protection, command-line flags to select local vs network targeting and partial-encryption ratios, and optional behaviors such as Base32-encoding original filenames and changing icons/wallpaper. Critically, S2W reports obtaining a working decryptor for certain DragonForce cases on both platforms: the Windows decryptor targets files with the .RNP extension, while the ESXi decryptor checks for .RNP_esxi files and a specific 8-byte magic value (build_key), potentially enabling recovery without ransom payment for affected victims. Separate reporting on DeadLock ransomware describes a different operation using Polygon smart contracts to rotate proxy infrastructure and is not part of the DragonForce activity.

Know this adversaryTTPs, infrastructure, and targeting history in one profile.
Get the profile
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

3 events · Dec 1, 2023 – Jan 14, 2026
  1. Jan 14, 202610mo ago

    S2W publishes technical analysis and obtains DragonForce decryptors

    On January 14, 2026, S2W published a detailed analysis of DragonForce ransomware, describing a custom build with heavy string obfuscation, ChaCha8 and RSA-4096 encryption, and configurable targeting options. S2W also reported obtaining working decryptors for both Windows and ESXi variants, which could help some victims recover without paying ransom.

  2. Jan 14, 202610mo ago

    DragonForce evolves into a RaaS operation targeting Windows and ESXi

    Following its initial forum activity, DragonForce developed into a full ransomware-as-a-service operation targeting both Windows systems and VMware ESXi environments. Its payload was reported to be derived from leaked LockBit 3.0 and Conti code and used for rapid encryption of local disks and network shares.

  3. Dec 1, 20233y ago

    DragonForce first appears on BreachForums

    DragonForce was first observed in December 2023 on BreachForums, where it advertised stolen data and presented itself as a cartel-style ransomware operation. This marked the earliest known public emergence of the group.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Threat actors

1 linked

Malware

1 linked

Affected products

2 linked
WindowsVmware Esxi

Observables

5 linked

Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?See this adversary's TTPs, infrastructure, and targeting history, correlated against your exposure.
Get the Full Actor Profile
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.