Join our Newsletter — 33% off our NHI Course
Home› Guides› ALPHV BlackCat Threat Actor Profile: Affiliate Model, Exit…
Guide Threat Intelligence & Threat Actors

ALPHV BlackCat Threat Actor Profile: Affiliate Model, Exit and Defences

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 26 October 2026 12 min read
On this page

ALPHV BlackCat showed how far a ransomware-as-a-service brand can reach when skilled affiliates bring their own identity attacks: help desk impersonation, MFA interception and stolen remote access logins. The operation ran from late 2021 until it vanished in March 2024, weeks after the Change Healthcare attack, yet its affiliates and tradecraft moved on to other brands. This profile draws on the joint #StopRansomware advisory AA23-353A from the FBI, CISA and HHS, the US Department of Justice, MITRE ATT&CK v20, Microsoft and the HHS Health Sector Cybersecurity Coordination Center. It covers names, the affiliate model and its collapse, techniques mapped to ATT&CK, identity abuse, and the defences that still apply. It is written for security operations, identity and healthcare security teams; it contains no leak-site material and names no individuals.

Key takeaways

  • The brand ended but the affiliates did not. ALPHV shut its infrastructure in March 2024 in what reporting described as an exit scam; the Change Healthcare data later surfaced with RansomHub, so defend against the techniques, not the name.
  • Identity attacks were the main entry. AA23-353A describes affiliates posing as IT or help desk staff by phone or SMS to obtain credentials, and using Evilginx2 to capture MFA codes and session cookies.
  • Remote access without MFA was decisive. Change Healthcare's CEO told Congress the compromised Citrix portal did not have multi-factor authentication; ALPHV claimed the attack and UnitedHealth paid USD 22 million.
  • Healthcare was singled out. After the December 2023 law enforcement action, the advisory reports an ALPHV administrator encouraging affiliates to target hospitals, and healthcare became the most commonly victimised sector.
  • The controls are known. Phishing-resistant MFA, verified help desk resets, allowlisted remote access tools, tier 0 protection for backup and hypervisor credentials, and immutable backups address most of what affiliates did.

Who they are (names and aliases)

The Department of Justice describes ALPHV, also known as BlackCat and Noberus, as the second most prolific ransomware-as-a-service variant in the world over the 18 months before December 2023. MITRE ATT&CK tracks the encryptor as software S1068, first observed in November 2021 and written in Rust. ATT&CK has no separate group entry for the operators, because the intrusions were carried out by many affiliates.

Name or IDSourceWhat it refers to
BlackCat (S1068)MITRE ATT&CKThe Rust encryptor; ATT&CK aliases ALPHV and Noberus; encrypts Windows, Linux and VMware instances
ALPHV, NoberusDepartment of Justice, MITRE ATT&CKNames for the same RaaS operation
SphynxAA23-353ARewritten "Ransomware 2.0" version announced in February 2023 with added evasion and affiliate tooling
ExMatterHHS HC3Data exfiltration tool used with BlackCat, updated in August 2022 to target specific file types
Affiliates: Scattered Spider (G1015)MITRE ATT&CKATT&CK records Scattered Spider deploying BlackCat
Affiliates: Pistachio Tempest, Velvet TempestMicrosoftFormerly DEV-0237 (also FIN12) and DEV-0504, both previously deploying other RaaS families

HHS HC3 notes that BlackCat is believed to be a successor to the DarkSide and BlackMatter operations; treat this as an assessment, not a proven lineage. See the Threat Actor Groups Guide for how naming schemes relate.

Targeting and motivation

  • Motivation: financial. The Department of Justice says the group's affiliates targeted more than 1,000 victims and received hundreds of millions of dollars in ransom payments.
  • Affiliate model: the operators developed the encryptor, ran the leak and negotiation sites, and recruited affiliates who breached networks and deployed it. HC3 notes affiliates also bought access to networks on underground forums.
  • Sectors and regions: ATT&CK records victims across Africa, the Americas, Asia, Australia and Europe in many sectors. HC3 warned of continued targeting of healthcare and public health.
  • Retaliatory targeting: AA23-353A says that of nearly 70 victims leaked since mid-December 2023, healthcare was the most commonly victimised, following the administrator's call to target hospitals.
  • Extortion beyond encryption: the advisory records affiliates extorting without deploying ransomware, offering unsolicited "vulnerability reports" as an incentive to pay, and HC3 notes DDoS against victims who refused. See the Ransomware Negotiation Guide.

Disruption and exit

DateEventSource
November 2021BlackCat first observedMITRE ATT&CK, HHS HC3
April 2022FBI FLASH publishes BlackCat indicatorsAA23-353A
February 2023Sphynx version announcedAA23-353A
19 December 2023Justice Department announces disruption; FBI decryptor offered to more than 500 victims, sparing ransom demands of about USD 68 million; joint advisory publishedDepartment of Justice, AA23-353A
21 February 2024Ransomware deployed at Change Healthcare after access on 12 FebruaryNHI Mgmt Group breach analysis
27 February 2024Advisory updated with healthcare targeting and new IOCsAA23-353A
5 March 2024Leak and negotiation sites go offline behind a seizure banner; Europol and the UK NCA told reporters they were not involved, and an affiliate claimed the operators kept the USD 22 million Change Healthcare paymentBleepingComputer

Tactics and techniques (MITRE ATT&CK)

IDs below are ATT&CK v20 entries recorded against S1068 or techniques AA23-353A and Microsoft describe. Defence impairment now sits under tactic TA0112 Defense Impairment.

TacticTechniqueWhat sources describePrimary defence
ReconnaissanceT1598 Phishing for InformationOpen source research on staff, then calls or SMS posing as IT or help deskVerified identity checks at the help desk
Credential accessT1557 Adversary-in-the-Middle; T1539 Steal Web Session CookieEvilginx2 capturing MFA codes, passwords and session cookiesFIDO2 or PKI-based MFA bound to origin
Initial accessT1133 External Remote Services; T1078 Valid Accounts; T1190 Exploit Public-Facing ApplicationCompromised credentials on RDP and remote access portals; unpatched Exchange (Microsoft)MFA on all remote access; patch KEV flaws
Command and controlT1219.002 Remote Desktop Software; T1572 Protocol TunnelingAnyDesk, Splashtop, ScreenConnect, SimpleHelp, MeshCentral; Plink and Ngrok; Brute Ratel C4 and Cobalt StrikeAllowlist approved remote tools
Credential accessT1003.001 LSASS Memory; T1558 Steal or Forge Kerberos Tickets; T1555 Credentials from Password StoresMimikatz, Rubeus, WDigest enabled for cleartext (Microsoft); passwords from domain controllers and backup servers (AA23-353A)Credential Guard; disable WDigest; isolate backup credentials
PersistenceT1136.002 Domain AccountUser account named "aadmin" createdAlert on account creation
Lateral movementT1570 Lateral Tool Transfer; T1569.002 Service ExecutionEncryptor spreads with PsExec using embedded credentialsBlock PsExec and WMI process creation where not needed
Defence impairmentT1685 Disable or Modify Tools; T1685.005 Clear Windows Event LogsPOORTRY and STONESTOP to kill security processes; wevtutil log clearing; Exchange logs clearedTamper protection; forward logs off-host
ExfiltrationT1567.002 Exfiltration to Cloud StorageMega.nz and Dropbox; ExMatter; Rclone (Microsoft)Egress controls on servers
ImpactT1486 Data Encrypted for Impact; T1490 Inhibit System Recovery; T1561.001 Disk Content WipeEncryption of Windows, Linux and VMware; shadow copies deleted; VM snapshots wipedImmutable, offline backups

Microsoft notes the payload needs an access token on its command line to run, which defenders can hunt for in process telemetry.

How they abuse identities and credentials

Human identities

  • Help desk social engineering: affiliates researched employees and then posed as IT staff to get credentials, or posed as the employee to the help desk. The MGM Resorts breach, claimed by ALPHV and reported as the work of a Scattered Spider affiliate, began with a help desk call that led to identity provider admin access. See the Account Recovery and Help Desk Security Guide.
  • MFA interception: Evilginx2 proxies the real login page and captures the session cookie after MFA completes, so OTP and push factors give no protection. See the AiTM Phishing Guide.
  • Single-factor remote access: in the Change Healthcare breach compromised credentials opened a Citrix portal without MFA on 12 February 2024, with encryption nine days later and 192.7 million people ultimately affected.

Privileged and non-human identities

  • Embedded domain credentials: HC3 notes the encryptor can be configured with domain credentials to spread through PsExec. Any credential an affiliate obtains becomes a deployment key, so tier 0 accounts must never log on to ordinary servers where they can be harvested.
  • Backup server secrets: AA23-353A reports passwords harvested from backup servers. Backup service accounts with domain admin rights hand over both data and the means to stop recovery. See the Backup Identity Isolation Guide.
  • Kerberos tickets: Rubeus and Kerberos ticket generation give domain access without a password. Service accounts with weak passwords are the usual target; replace them with group managed service accounts. See the Credential Dumping Guide.
  • Hypervisor access: encryption of VMware instances requires hypervisor credentials. See the ESXi Ransomware Playbook.

Notable incidents

WhenVictimWhat sources describe
September 2023MGM ResortsALPHV claimed the attack and said it encrypted more than 100 ESXi hypervisors (not confirmed by MGM); MGM's 8-K estimated about USD 100 million impact
February 2024Change HealthcareCitrix login without MFA; USD 22 million paid by UnitedHealth; nationwide claims and pharmacy disruption; data later held by RansomHub

The pattern of affiliates switching brands is why the RansomHub Threat Actor Profile and the Scattered Spider Threat Actor Profile are useful companions to this page.

Detection and defence

Phased response for a defender

  1. First week, close single-factor remote access: list every VPN, Citrix, RDP gateway and remote support portal and confirm MFA for every account. Where MFA is impossible, restrict by source address and schedule replacement.
  2. Harden the help desk: require call-back to a number on file, manager approval or in-person verification before any password or MFA reset for privileged users. Log every reset and alert on resets followed by new MFA device registration.
  3. Move administrators to phishing-resistant MFA: FIDO2 security keys or platform passkeys, as AA23-353A recommends. Pilot with IT staff, keep a break-glass account, then extend. See the Phishing-Resistant MFA Guide.
  4. Allowlist remote access tools: the advisory asks for application control that blocks unlisted and portable remote access software. Run in audit mode first and roll back by returning the policy to audit.
  5. Protect credentials: enable Credential Guard and LSA protection, keep WDigest disabled, use LAPS for local admin passwords, and apply attack surface reduction rules for LSASS theft and PsExec or WMI process creation, as Microsoft recommends.
  6. Isolate recovery: separate backup and hypervisor administration from the production domain and keep immutable offline copies.

What to log and alert on

SignalSourceWhy it matters
Password or MFA reset followed by new MFA device registration within an hourIdentity provider audit logs, help desk ticketsHelp desk impersonation pattern
Session token used from a new ASN or device shortly after sign-inIdentity provider sign-in logsAiTM session cookie replay
Events 4720 and 4728 (account created, added to a privileged group)Domain controller Security logNew accounts such as "aadmin"
Registry change setting UseLogonCredential to 1 under WDigestSysmon event 13, EDREnables cleartext credential theft
Command lines containing --access-token; PsExec service creation (event 7045)EDR, System logBlackCat execution and spreading
Event 1102 (Security log cleared), wevtutil cl; Mega, Dropbox or Ngrok traffic from serversSecurity log, proxy and DNS logsDefence impairment and exfiltration

Metrics that show it is working

  • Phishing-resistant MFA coverage: share of privileged and remote access accounts on FIDO2 or PKI-based factors.
  • Verified reset rate: share of privileged credential resets with documented out-of-band verification; target 100 per cent.
  • Unapproved remote tools: count of remote access products seen in EDR beyond the approved list; target zero.
  • Privileged change triage time: minutes from a 4728 event on a tier 0 group to analyst review.
  • Restore success: share of quarterly restore tests that meet the recovery time objective.

Decision guidance

Smaller organisations get the most from MFA on every remote access path, a simple call-back rule at the help desk, a managed detection service that watches identity logs, and an offline backup. Larger organisations, especially in healthcare, should move administrators to phishing-resistant MFA, treat identity provider, backup and hypervisor administration as tier 0, and run tabletop exercises against an affiliate that already has valid credentials. See the Healthcare Identity Security Guide.

Framework mapping

Control areaNIST SP 800-53 Rev. 5NIST CSF 2.0
MFA on remote and privileged accessAC-17, IA-2(1)PR.AA-03
Social engineering awarenessAT-2PR.AT-01
Least privilege for admin accountsAC-6(5)PR.AA-05
Allowlist remote access softwareCM-7(5)PR.PS-02
Monitoring and log reviewSI-4, AU-6DE.CM-01, DE.CM-03
Protected backupsCP-9PR.DS-11

Practitioner checklist

  • Enforce MFA on every VPN, Citrix, RDP and remote support portal, with no single-factor exceptions.
  • Require out-of-band verification for privileged password and MFA resets at the help desk.
  • Move administrators to FIDO2 or PKI-based MFA to defeat AiTM kits such as Evilginx2.
  • Block unapproved and portable remote access tools with application control.
  • Enable Credential Guard and LSA protection, keep WDigest disabled and deploy LAPS.
  • Alert on new privileged accounts, log clearing and --access-token command lines.
  • Separate backup and hypervisor credentials from the production domain and keep immutable backups.
  • Track affiliates, not brands: map detections to the techniques in AA23-353A and test them.

Standards and references

Related NHI Mgmt Group resources: Ransomware Groups Guide · Scattered Spider Threat Actor Profile · Medusa Ransomware Threat Actor Profile · Phishing-Resistant MFA Guide · Ransomware Response and Recovery Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 26 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.