Ransomware brands die far more often than the people and code behind them, so an incident labelled with a "new" name is often an old operation with a fresh leak site. When BlackSuit appears where Royal used to be, or a Hive successor emerges months after a takedown, the lineage changes what responders should hunt for, whether a payment may breach sanctions, which decryptors might work and how much weight to give the gang's promises. This guide explains the ways ransomware operations rebrand and split, maps documented lineages with the evidence and confidence behind each, and shows how to record lineage in a threat intelligence programme so it drives detection and payment decisions. It is for threat intelligence analysts, incident responders, legal and insurance teams supporting a ransomware response, and detection engineers. It goes deeper than the overview in the Ransomware Groups Guide and does not repeat its group-by-group profiles.
Key takeaways
- Rebrand is one of six patterns. A renamed operation, a splinter crew, purchased or leaked source code, migrating affiliates, a sanctioned group hiding inside another brand, and simple name reuse all look like "a new group" on a leak site, and each has different consequences.
- Confidence must travel with the claim. CISA states as fact that BlackSuit is the evolution of Royal; Cisco Talos assesses Chaos as likely formed by former BlackSuit members with moderate confidence; Group-IB links Hunters International to Hive with moderate confidence. Record the source and confidence, not just the arrow.
- Sanctions follow people, not names. OFAC can impose civil penalties on a strict liability basis, and Mandiant assessed that Evil Corp linked actors moved to LockBit likely to hinder attribution and evade sanctions. A brand change does not remove sanctions exposure.
- Lineage predicts tradecraft. Talos mapped Chaos command-line options one for one onto BlackSuit's, and ATT&CK records Conti overlaps in Royal and Akira. Detections built for the parent usually transfer to the child.
- Takedowns reset the label, not the threat. The FBI held Hive's keys for months before the January 2023 takedown, yet a probable successor was operating by October 2023. Plan for the next brand on day one of any disruption.
Why lineage matters in a live incident
A leak site name is a marketing asset chosen by criminals. The decisions an organisation makes during a ransomware incident depend on who is really behind it and what code they run.
| Decision | What lineage tells you | Who uses it |
|---|---|---|
| Payment and sanctions screening | Whether the operators, wallets or infrastructure connect to a designated person or entity, whatever the current brand | Legal, insurers, negotiators, financial institutions |
| Hunting scope | Which persistence, credential theft and exfiltration techniques the parent used, so you know where else to look | Incident responders, threat hunters |
| Decryption options | Whether a law enforcement key release, a public decryptor or a known encryption flaw for the parent family might apply | Recovery team |
| Credibility of promises | Whether the lineage includes exit scams, re-extortion or data published despite payment | Executives, negotiators |
| Detection engineering | Which encryptor command-line options, ransom note patterns and tooling are inherited | Detection engineers, SOC |
| Reporting and attribution | Which name to use in regulator and law enforcement reports so they link to existing cases | CISO, legal |
See the Ransomware Payments and Sanctions Guide and the Ransomware Negotiation Guide for the decisions this intelligence feeds.
Six ways a ransomware brand changes
| Pattern | What happens | Documented example | Main consequence |
|---|---|---|---|
| Rebrand (same operators, new name) | Operators retire a name, often after heat from law enforcement or publicity, and continue with updated code | Royal to BlackSuit: CISA states BlackSuit "is the evolution of the ransomware previously identified as Royal" and shares numerous coding similarities | Treat as the same actor for sanctions, TTPs and history |
| Successor or splinter | Some members form a new crew after a shutdown, carrying playbooks and tooling | Chaos, assessed by Talos with moderate confidence as likely formed by former BlackSuit (Royal) members, emerging from February 2025 | Expect inherited TTPs; ownership and sanctions links must be re-examined |
| Code purchase or acquisition | A new operation buys source code, panel or infrastructure from a closing one | ATT&CK records that RansomHub operators may have purchased and rebranded resources from Knight (formerly Cyclops); Hunters International's administrator claimed to have bought Hive's source code | Encryptor behaviour transfers; people may not |
| Leaked code or builder | Source or a builder becomes public and unrelated actors deploy it | ATT&CK lists LockBit 3.0 as having similarities to BlackMatter and BlackCat; the LockBit Threat Actor Profile covers the leaked LockBit 3.0 builder | The family name on disk no longer identifies the operator |
| Affiliate migration | Affiliates move to a rival RaaS, taking access and stolen data with them | After the ALPHV shutdown, the affiliate behind the Change Healthcare Breach 2024 moved the stolen data to RansomHub, which demanded a further payment | Paying one brand does not end exposure to its affiliates |
| Hiding inside another brand | A sanctioned or exposed group deploys a third party's RaaS to obscure attribution | Mandiant assessed with high confidence that UNC2165, which overlaps Evil Corp, shifted to LOCKBIT "likely to hinder attribution efforts in order to evade sanctions" | The visible brand understates sanctions risk |
Name reuse is not lineage. Talos notes the 2025 Chaos group appears unrelated to earlier Chaos builder variants and uses the same name, apparently to create confusion. The Ransomware Groups Guide lists further collisions, such as Medusa and MedusaLocker. Always pair a name with a hash, an ATT&CK software ID or a source report. See the Threat Actor Naming Conventions Guide.
Documented lineages and how strong the evidence is
The table lists lineages stated in government sources, MITRE ATT&CK v20 or named vendor research read for this guide. "Stated" means the source presents it as fact; otherwise the source's own confidence wording is kept.
| Lineage | Relationship as the source puts it | Strength | Source |
|---|---|---|---|
| Conti (S0575) to Royal (S1073) | Similarities in encryption routines and TTPs; possible connection between operators | Possible | MITRE ATT&CK v20 |
| Royal (S1073) to BlackSuit | BlackSuit is the evolution of Royal, with numerous coding similarities | Stated | CISA and FBI AA23-061A (August 2024 update) |
| BlackSuit to Chaos (2025) | Likely formed by former BlackSuit members, or a rebrand | Moderate confidence | Cisco Talos |
| Conti to Akira (G1024, S1129) | Multiple overlaps with Conti ransomware | Technical overlap | MITRE ATT&CK v20 |
| Conti to Black Basta (S1070) | Operators could include current or former Conti members | Possible | MITRE ATT&CK v20 |
| Hive to Hunters International to World Leaks | Possible rebrand of Hive; extortion-only World Leaks launched 1 January 2025 | Moderate confidence | Group-IB |
| Cyclops to Knight to RansomHub (S1212) | Operators may have purchased and rebranded Knight resources | Probable | MITRE ATT&CK v20 |
| GandCrab to REvil (S0496) | REvil shares code similarities with GandCrab | Code similarity | MITRE ATT&CK v20 |
| ChaCha to Maze (S0449) to Egregor (S0554) | Maze previously known as ChaCha; Egregor has code similarities with Maze and Sekhmet | Code similarity | MITRE ATT&CK v20 |
| Hermes to Ryuk (S0446) | Ryuk shares code similarities with Hermes | Code similarity | MITRE ATT&CK v20 |
| Indrik Spider (G0119): BitPaymer (S0570), WastedLocker (S0612), Hades, then LockBit | Sequence of closely related variants; shift to LockBit after sanctions | High confidence (shift to LockBit) | MITRE ATT&CK v20; Mandiant |
| CryptoMix to Clop (S0611) | Clop is a variant of CryptoMix | Stated | MITRE ATT&CK v20 |
Per-family detail sits in the individual profiles: Conti Ransomware Profile Guide, Royal and BlackSuit Ransomware Profile Guide, Hunters International Threat Actor Profile and RansomHub Threat Actor Profile.
How to assess a lineage claim
Lineage claims spread quickly on social media and in vendor blogs. Weigh the evidence type before acting on one.
| Evidence type | Example from the sources | Weight | Caveat |
|---|---|---|---|
| Law enforcement or government statement | CISA on Royal to BlackSuit; DOJ treating "BlackSuit (Royal)" as one group | High | May lag reality by months |
| Shared private infrastructure or contacts | Hive's instant messaging contact reappearing with Hunters International | High when verified | Hard to verify independently |
| Encryptor code and parameter similarity | Chaos /lkey, /encrypt_step and /kill_vms mapping to BlackSuit -id, -ep and -stopvm | Medium to high | Leaked or purchased code produces the same signal without the same people |
| Ransom note structure and negotiation style | Chaos notes resembling Royal and BlackSuit notes | Medium | Easy to copy deliberately |
| Intrusion TTPs | Shared use of LOLbins and RMM tools | Low to medium | Affiliates move between brands and many TTPs are common to all |
| Underground chatter or the group's own claims | Hunters International claiming to have bought Hive code; forum users calling it Hive | Low unless corroborated | Criminals lie for reputation and to confuse attribution |
Practical rule: require at least one high-weight item, or two independent medium-weight items, before treating a lineage as established in a payment or sanctions decision. For detection, a medium-weight code link is enough to borrow the parent's detections, because a false positive there costs little.
Sanctions and payment decisions
OFAC's updated advisory of 21 September 2021 is the reference point for US sanctions exposure.
- Strict liability: OFAC may impose civil penalties even if the payer did not know, or have reason to know, that the transaction involved a sanctioned person.
- Who it is aimed at: the advisory names cyber insurers, digital forensics and incident response firms, and financial institutions that may process payments, alongside victims.
- Licences: applications to pay are reviewed case by case with a presumption of denial.
- Mitigating factors: a risk-based sanctions compliance programme, meaningful cyber security measures such as offline backups and incident response plans, self-initiated and prompt reporting to law enforcement or CISA, and full cooperation.
- Designations behind rebrands: Evil Corp was designated in December 2019. On 1 October 2024 the US designated seven more individuals and two entities, with the UK designating 15 members and affiliates and Australia three. Mandiant reported that after Evil Corp's public association with WastedLocker and Hades, the actors faced challenges receiving payments and that some negotiators refuse to facilitate payments to known sanctioned entities, which is the incentive to hide behind another brand.
What lineage work adds: sanctions screening of a wallet address alone misses a rebranded operation that has rotated wallets. Record in the decision log every lineage hypothesis considered, its evidence and confidence, and the screening done against each predecessor name. That record is evidence of the "risk-based" compliance programme OFAC lists as mitigating. This guide summarises sanctions guidance for security teams and is not legal advice; decisions belong with counsel.
Turning lineage into detections
Lineage is most useful when it changes what the SOC looks for. Map inherited behaviour to ATT&CK v20 and reuse the parent's analytics.
| Inherited behaviour | ATT&CK v20 | What to carry forward |
|---|---|---|
| Encryptor command-line options for key ID, partial encryption and VM shutdown | T1486 Data Encrypted for Impact; T1489 Service Stop | Command-line patterns from the parent family, renamed options as in the Chaos and BlackSuit mapping |
| Partial and multithreaded encryption | T1486 | File write-rate and entropy analytics tuned for intermittent encryption (Royal, INC Ransomware) |
| Hypervisor targeting | T1486; T1489 | ESXi shell and VM power-off monitoring. See the ESXi Ransomware Playbook |
| Recovery inhibition | T1490 Inhibit System Recovery | Shadow copy and backup catalogue deletion alerts |
| Defence impairment | T1685 Disable or Modify Tools | EDR tamper and driver load alerts from the parent's playbook |
| Remote tools and initial access | T1219 Remote Access Tools; T1133 External Remote Services; T1566 Phishing | The parent's preferred RMM and VPN access patterns; CISA lists phishing, RDP and initial access brokers for BlackSuit |
| Exfiltration before encryption | T1567.002 Exfiltration to Cloud Storage; T1048 Exfiltration Over Alternative Protocol | Rclone and bulk upload detections; extortion-only successors such as World Leaks keep this stage and drop encryption |
See the Data Extortion Without Encryption Guide for successors that stop encrypting altogether.
Where identity fits
Lineage also explains why credentials stolen under one brand are used under another. Affiliates and initial access brokers keep their footholds when a RaaS closes, so VPN accounts, service account passwords and remote management credentials compromised in a "BlackCat" intrusion remain live for whichever programme the affiliate joins next. CISA lists initial access brokers sourcing VPN credentials from stealer logs among BlackSuit's routes in. After any ransomware incident, or a disruption of a brand you were exposed to, rotate every credential the intrusion could have touched rather than only those named in the incident report. See the Initial Access Brokers Guide and the Service Account Security Guide.
Building lineage into your threat intelligence programme
- Adopt one identifier scheme: key every family to its ATT&CK software ID (for example S1073 Royal) and every operator cluster to a group ID where one exists, with vendor names as aliases.
- Model relationships explicitly: in a threat intelligence platform, use STIX 2.1 relationships such as
variant-ofbetween malware objects andderived-frombetween intrusion sets, each with a confidence value, source reference and date. - Attach evidence types: tag each link with the evidence classes from the assessment table so analysts can see whether it rests on a government statement, code or chatter.
- Link detections to families: store which analytics cover each family, so a new child inherits the parent's detection set automatically and gaps are visible.
- Watch disruption events: when law enforcement announces a takedown, such as Hive in January 2023 or BlackSuit in July 2025, open a watch item for successors and review in 30, 90 and 180 days.
- Feed the incident playbook: add a lineage and sanctions screening step to the ransomware playbook, owned by threat intelligence, with output to legal before any payment discussion. See the Ransomware Playbook Template.
- Test it: run a tabletop where the leak site shows an unknown brand and the team must produce a lineage hypothesis, confidence and sanctions view within four hours.
Small versus large organisations: a small organisation does not need its own lineage database; it needs its incident response retainer and insurer to document lineage and sanctions screening, and a question in the playbook asking them to. Large organisations and those in regulated sectors should hold lineage in their threat intelligence platform and review it quarterly.
Metrics
- Percentage of tracked ransomware families with an ATT&CK ID, aliases and at least one parent or child relationship recorded with confidence.
- Time from a new brand appearing in your sector to a recorded lineage hypothesis.
- Percentage of inherited behaviours from parent families covered by an active detection.
- Ransomware incidents where lineage and sanctions screening was documented before any payment discussion (target 100 percent).
- Successor watch items opened and closed after each publicised takedown.
Framework mapping
| Activity | NIST CSF 2.0 | NIST SP 800-53 Rev. 5 |
|---|---|---|
| Collect and analyse threat intelligence on ransomware lineages | ID.RA-02, ID.RA-03 | PM-16, RA-3 |
| Share and receive intelligence with partners | ID.RA-02 | SI-5 |
| Incident analysis and attribution during response | RS.AN-03 | IR-4 |
| Reporting to law enforcement and authorities | RS.CO-02 | IR-6 |
| Detection coverage for inherited behaviour | DE.CM-01, DE.AE-02 | SI-4 |
Common failure patterns
- Trusting the leak site name: responders scope the hunt to the brand's published TTPs and miss persistence inherited from the parent family.
- Screening the wallet, not the lineage: sanctions checks run only on the payment address, so a rebranded or hidden sanctioned group is missed.
- Arrows without confidence: a moderate-confidence vendor hypothesis becomes "fact" in an internal report and then drives a payment refusal or approval.
- Assuming a takedown ended the risk: credentials and access from an affiliate's earlier intrusion are not rotated, and the same access returns under a new brand.
- Paying to end exposure: the Change Healthcare case shows an affiliate taking data from a closed RaaS to a new one for a second demand. A payment buys a promise from one brand, not from the people who hold the data.
- Confusing name reuse with lineage: the 2025 Chaos group and older Chaos builder variants share only a name, and analytics borrowed from the wrong family waste effort.
Lessons from incidents
The Change Healthcare Breach 2024 illustrates several lineage effects at once: ALPHV claimed the attack, UnitedHealth paid a $22 million ransom, ALPHV shut down in what was widely reported as an exit scam, and the affiliate took the stolen data to RansomHub, which demanded a further payment. Two lessons follow. First, the relationship that matters is with the affiliate who holds the data, not the brand. Second, an operator's history of exit scams and affiliate disputes is part of its lineage and should inform any judgement about whether a payment would end the extortion. The BlackSuit takedown points the same way: DOJ announced the seizure of four servers, nine domains and about $1.09 million in virtual currency in August 2025, while Talos had already reported a probable successor, Chaos, operating since February 2025.
Practitioner checklist
- Key every ransomware family you track to an ATT&CK software ID and list vendor aliases.
- Record parent and child relationships with source, evidence type, confidence and date.
- Add a lineage and sanctions screening step to the ransomware playbook before any payment discussion.
- Screen predecessor names and known designated actors, not only the current wallet address.
- Copy parent-family detections to every assessed successor and test them.
- Open a successor watch item after each publicised takedown and review at 30, 90 and 180 days.
- Rotate all credentials an intrusion could have reached, even after the brand disappears.
- Ask your incident response retainer and insurer how they document lineage and sanctions checks.
- Run a tabletop with an unknown brand on the leak site and time the lineage assessment.
Standards and references
- CISA and FBI: #StopRansomware: BlackSuit (Royal) Ransomware (AA23-061A)
- US Treasury OFAC: Updated Advisory on Potential Sanctions Risks for Facilitating Ransomware Payments
- US Treasury: Sanctions on Evil Corp members and affiliates (1 October 2024)
- US Department of Justice: Coordinated Disruption Actions Against BlackSuit (Royal) Ransomware
- US Department of Justice: Disruption of the Hive Ransomware Variant
- MITRE ATT&CK: Software (ransomware family entries)
- Mandiant: To HADES and Back: UNC2165 Shifts to LOCKBIT to Evade Sanctions
- Cisco Talos: Research on the new Chaos ransomware group
Related NHI Mgmt Group resources: Ransomware Groups Guide · Ransomware-as-a-Service Business Model Guide · Cybercrime Law Enforcement Takedowns Guide · Ransomware Response and Recovery Guide · Threat Actor Groups Guide