Join our Newsletter — 33% off our NHI Course
Home› Guides› 8Base Ransomware Profile: Phobos Affiliate Tactics, Takedown and…
Guide Threat Intelligence & Threat Actors

8Base Ransomware Profile: Phobos Affiliate Tactics, Takedown and Defences

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 13 min read
On this page

8Base was a data extortion crew that rented the Phobos ransomware strain, broke into small and medium-sized organisations through phishing and exposed remote access, and stole data before encrypting it. This profile is built only from government and primary vendor research: the HHS Health Sector Cybersecurity Coordination Center (HC3) analyst note of November 2023, the joint FBI, CISA and MS-ISAC #StopRansomware advisory on Phobos (AA24-060A), the US Department of Justice and Europol announcements of the February 2025 disruption, and Cisco Talos malware research. It covers who 8Base was, how it related to Phobos, its techniques mapped to MITRE ATT&CK v20, the takedown and decryptor, and the detections and controls that break the playbook. It is written for security operations, infrastructure and identity teams. Attribution follows each source's own wording, and the page names no individuals.

Key takeaways

  • An affiliate, not a malware author. HC3 found 8Base deploying Phobos ransomware loaded by SmokeLoader, and the DOJ describes 8Base and "Affiliate 2803" as names used by a group deploying Phobos.
  • Small and medium organisations were the core target. HC3 reported professional services, manufacturing, construction, finance and healthcare victims, mostly in the US, Brazil and the UK.
  • Entry was ordinary. Phishing attachments and brute-forced or stolen RDP credentials (T1566.001, T1110, T1133) did the work, so phishing-resistant MFA and closed RDP remove most of the opportunity.
  • Recovery was the deliberate casualty. Shadow copies, backup catalogues and boot recovery were removed (T1490) before encryption of every connected drive (T1486), which is why offline, immutable backups decide the outcome.
  • Disrupted, not erased. The February 2025 operation brought arrests and disruption of over 100 servers, and Japan's National Police Agency later released a free decryptor, but Phobos techniques remain common across other affiliates.

Who they are (names and aliases)

8Base surfaced publicly in 2023 with a leak site and a Telegram channel. HC3 dated the earliest leak site posts to March 2022, suggesting roughly a year of quieter operation, and recorded a sharp rise in activity in May and June 2023. The Ransomware Groups Guide places 8Base in the wider affiliate economy; this page goes into the group itself.

AttributeWhat the sources saySource
Names8Base; "Affiliate 2803" among other names used by the same groupDOJ, February 2025
MalwarePhobos ransomware (HC3 observed version 2.9.1), delivered and unpacked by the SmokeLoader backdoorHC3, Cisco Talos
Earlier campaign nameTalos believes the older "Eight" Phobos variant was run by the group now operating 8BaseCisco Talos
Relationship to RansomHouseHC3 found the 8Base ransom note a 99% textual match to RansomHouse's and the leak site wording copied, but said it was unclear whether 8Base was an offshoot or a copycatHC3
Business modelDouble extortion: data theft plus encryption, with HC3 stressing the data theft focusHC3
MITRE ATT&CK entryNo ATT&CK group or software entry for 8Base in ATT&CK v20; technique mappings below come from HC3 and AA24-060AMITRE ATT&CK v20
StatusLeadership arrests and infrastructure disruption announced in February 2025DOJ, Europol

How the Phobos affiliate model shaped 8Base

The DOJ describes how Phobos worked: affiliates broke into a network and deployed the ransomware, each deployment carried a unique alphanumeric string matched to a decryption key, and affiliates paid a fee to Phobos administrators for that key into a wallet unique to each affiliate. Cisco Talos assessed with moderate confidence that Phobos was closely managed by a central authority, because every sample it studied shared the same public RSA key. Talos also found that each build's configuration carries an extension blocklist naming other groups that use Phobos, which links builds to affiliates. For defenders the practical point is that the file extension and contact address on encrypted files identify the affiliate, not the malware: an 8Base sample analysed by Talos appended an extension ending in .8base containing a victim ID and a contact address, and the strings change per campaign.

Targeting and motivation

8Base was financially motivated. HC3 described a focus on small and medium-sized businesses, with professional services such as accounting, legal and business services most affected, followed by manufacturing, construction, finance and insurance, and healthcare. Victims were mostly in the United States, Brazil and the United Kingdom, with others in Australia, Germany, Canada, China and India; HC3 noted no victims in former Soviet or CIS countries. HC3 reported that in July 2023, 8Base, Cl0p and LockBit together accounted for 48% of recorded attacks. See the Cl0p Threat Actor Profile and the LockBit Threat Actor Profile for those groups.

The DOJ said the wider group behind 8Base was linked to more than 1,000 public and private victims worldwide and more than $16 million in ransom payments, and that victims included a children's hospital, healthcare providers and educational institutions. Treat those totals as allegations in an indictment: the DOJ itself states that an indictment is merely an allegation and defendants are presumed innocent until proven guilty.

Tactics and techniques (MITRE ATT&CK)

The table maps behaviour reported by HC3 for 8Base and by AA24-060A for Phobos affiliates, including 8Base, to ATT&CK v20. AA24-060A predates the ATT&CK v20 reorganisation of defence evasion, so firewall and tool tampering are shown under the current Defense Impairment techniques. Every ID was checked against ATT&CK v20.

TacticBehaviour reportedATT&CK v20Source
ReconnaissanceScanning IP ranges for exposed RDPT1595.001 Scanning IP BlocksAA24-060A
Initial accessPhishing emails with malicious attachmentsT1566.001 Spearphishing Attachment; T1204.002 Malicious FileHC3, AA24-060A
Initial accessBrute force against RDP, then logging in as a valid userT1110 Brute Force; T1133 External Remote Services; T1078 Valid AccountsAA24-060A
PersistenceStartup folder and Run registry key entries, payload copies in AppDataT1547.001 Registry Run Keys / Startup FolderHC3, Talos
StealthPacked payloads unpacked by SmokeLoader; mshta used to run files and show ransom notesT1027.002 Software Packing; T1218.005 MshtaHC3, AA24-060A
Privilege escalationProcess injection into memoryT1055.002 Portable Executable InjectionAA24-060A
Defense impairmentWindows firewall turned off; security and office processes terminatedT1686 Disable or Modify System Firewall; T1685 Disable or Modify ToolsHC3, Talos, AA24-060A
Credential accessLSASS memory dumping, cached domain credentials, browser and password manager storesT1003.001 LSASS Memory; T1003.005 Cached Domain Credentials; T1555.003; T1555.005AA24-060A, Talos
DiscoveryDomain account, file and network share enumerationT1087.002 Domain Account; T1083; T1135 Network Share DiscoveryHC3, AA24-060A
Command and controlCommercial remote access software installed (Talos observed AnyDesk)T1219 Remote Access ToolsTalos, AA24-060A
ExfiltrationData archived, then sent by WinSCP to attacker FTP or to Mega cloud storageT1560; T1071.002 File Transfer Protocols; T1567.002 Exfiltration to Cloud StorageAA24-060A
ImpactShadow copies and backup catalogues deleted, boot recovery disabled, connected drives and shares encrypted, extortion by email and leak siteT1490 Inhibit System Recovery; T1486 Data Encrypted for Impact; T1657 Financial TheftHC3, Talos, AA24-060A

AA24-060A names the tools seen across Phobos intrusions: SmokeLoader, Cobalt Strike, BloodHound and SharpHound, Mimikatz, NirSoft and Remote Desktop PassView utilities, Angry IP Scanner, WinSCP, Mega and process tools such as Process Hacker and PowerTool. Most are legitimate or dual-use, so detection has to rest on context: who ran them, from where and when.

How they abuse identities and credentials

Every stage of the 8Base intrusion path depends on credentials. A brute-forced or reused RDP password gives the first interactive session. LSASS dumping and cached domain credentials then turn one workstation into domain reach, and the advisory notes theft from browsers and password managers, which often hold service and administrator passwords. AA24-060A also notes that password manager databases were among the data targeted for exfiltration.

  • Remote access accounts: any account that can log in over RDP without MFA is an entry point. The advisory calls for phishing-resistant MFA, lockouts and logging on RDP (CPG 2.W, 2.H). See the Exposed RDP Compromise guide.
  • Privileged accounts: place domain administrators in the Protected Users group, apply time-based access to admin accounts (CPG 2.A, 2.E) and keep plaintext credentials out of scripts, as AA24-060A recommends. See the Credential Dumping Guide.
  • Unknown accounts: review domain controllers, servers, workstations and Active Directory for accounts you do not recognise (CPG 4.C), because new local or domain accounts are a common persistence step.
  • Backup and recovery identities: the deletion of backup catalogues needs rights on the systems holding them. Separate backup administration from the production domain. See the Backup Identity Isolation Guide.

The 2025 takedown and decryptor

DateEventSource
November 2023HC3 publishes its 8Base analyst note; Cisco Talos publishes Phobos and 8Base malware and affiliate researchHC3, Talos
29 February 2024FBI, CISA and MS-ISAC publish #StopRansomware: Phobos Ransomware (AA24-060A)CISA, IC3
June and November 2024An alleged Phobos administrator is arrested in South Korea and later extradited to the United StatesEuropol
10 February 2025DOJ unseals charges against two alleged operators of the group using the 8Base and Affiliate 2803 names; Europol reports four arrests of people leading 8Base; over 100 servers disruptedDOJ, Europol
July 2025Japan's National Police Agency publishes a free decryption tool and guide for Phobos and 8Base victims, shared by the European Cybercrime Centre and the FBIThe Record

The FBI's Baltimore Field Office led the investigation with Europol, the US Department of Defense Cyber Crime Center and partners in the UK, Germany, Japan, Spain, Belgium, Poland, the Czech Republic, France, Thailand, Finland, Switzerland and Romania, according to the DOJ. Two lessons follow. First, organisations with older Phobos-encrypted data should check the NPA tool before writing it off, and keep encrypted copies for that reason. Second, takedowns remove operators, not techniques: Talos found hundreds of contact addresses tied to Phobos campaigns, and the same access, credential and recovery-destruction steps appear across many affiliates. The Hive Ransomware profile shows the same pattern after an earlier disruption.

Detection and defence

What to monitor

SignalWhere to see itTechnique it catches
Bursts of failed logons from one source against RDP hosts (Windows Security event 4625) followed by a success (4624)Domain controller and server security logs, VPN and firewall logsT1110, T1133
Windows Firewall disabled or rules changed by a non-admin processWindows Firewall audit events, EDRT1686
New Run keys or Startup folder entries pointing at AppDataEDR, Sysmon registry and file eventsT1547.001
Handle access to LSASS by unexpected processesEDR, Sysmon process access eventsT1003.001
Shadow copy deletion, backup catalogue deletion or boot configuration changes via built-in utilitiesEDR command line telemetry, process creation event 4688 with command line loggingT1490
WinSCP, Mega or new remote access software on servers that never use themApplication allowlisting logs, proxy and DNS logsT1071.002, T1567.002, T1219
Large outbound transfers of .rar or .zip archivesNetwork flow, proxy, DLPT1560, T1048

For the event IDs and EDR data sources behind these signals, see the EDR Telemetry Guide. AA24-060A also publishes indicators (domains, IP addresses, hashes, contact addresses) with STIX files; use them for retrospective hunting, but expect them to age quickly.

Controls that break the playbook

  1. Close or gate RDP first. Audit every system exposing RDP, remove internet exposure, put access behind a VPN or gateway with phishing-resistant MFA, and enforce lockouts (CPG 2.W, 2.H). See the Remote Desktop (RDP) Security Guide.
  2. Harden against phishing attachments. Add external email banners and disable hyperlinks in inbound email (CPG 2.M), and train staff to report attachments.
  3. Control what can run. Allowlist remote access tools and block portable executables where possible, as AA24-060A recommends. See the Application Allowlisting Guide.
  4. Protect credentials. Enable LSASS protection features, use Protected Users for domain admins and apply least privilege to admin accounts (CPG 2.E).
  5. Make backups survive. Keep offline, encrypted, immutable backups and test restores regularly (CPG 2.R). See the Backup Security and Immutable Backup Guide.
  6. Segment and watch lateral movement. Segment networks (CPG 2.F) and monitor internal traffic (CPG 3.A) so one workstation cannot reach every share.
  7. Rehearse the response. Use the Ransomware Playbook Template, and report incidents to the FBI, IC3 or CISA as the advisory asks, with ransom notes, contact addresses and encrypted file samples preserved.

Framework mapping

DefenceNIST CSF 2.0NIST SP 800-53 Rev. 5CISA CPG (per AA24-060A)
Phishing-resistant MFA on remote accessPR.AA-03IA-2(1), IA-2(2)2.H, 2.W
Least privilege and time-based adminPR.AA-05AC-6, AC-22.A, 2.E
Immutable, tested backupsPR.DS-11CP-9, CP-102.R
Logging and anomaly detectionDE.CM-01, DE.CM-09AU-6, SI-42.T, 3.A
Allowlisting and unused services disabledPR.PS-05CM-72.N, 2.V

Measuring progress

  • RDP exposure: count of internet-reachable RDP endpoints, target zero.
  • MFA coverage: share of remote access and webmail logins protected by phishing-resistant MFA.
  • Restore readiness: time to restore a tier 1 server from an immutable copy in the last test.
  • Detection latency: median time from firewall tampering or shadow copy deletion to an analyst alert.
  • Privileged account hygiene: number of domain admin accounts outside Protected Users or without time-bound access.

Common failure patterns

  • Treating SMEs as unattractive: 8Base made a business of smaller firms, so "too small to target" planning leaves RDP and backups exposed.
  • MFA on email but not remote desktop: brute force on RDP succeeds wherever a password alone opens a session.
  • Online backups in the same domain: backup catalogues and shadow copies deleted with stolen admin rights leave nothing to restore.
  • Ignoring firewall changes: the firewall being switched off is an early, loud signal that many teams do not alert on.
  • Hunting by extension alone: Phobos extensions and contact addresses change per affiliate and campaign, so behaviour-based detection outlasts string matching.

Practitioner checklist

  • Inventory and remove internet-facing RDP; require phishing-resistant MFA on every remaining remote access path.
  • Alert on RDP brute force patterns, firewall disablement, LSASS access and shadow copy deletion.
  • Allowlist approved remote access tools and block WinSCP, Mega and similar where they have no business use.
  • Place domain admins in Protected Users and move admin access to time-bound elevation.
  • Review Active Directory and local accounts for unknown entries each month.
  • Keep offline, immutable backups under separate credentials and run a restore test this quarter.
  • Load AA24-060A indicators into your SIEM for a retrospective hunt.
  • For any historic Phobos-encrypted data, check the Japan NPA decryptor guide before discarding it.

Standards and references

Related NHI Mgmt Group resources: Ransomware Groups Guide · Equation Group · Exposed RDP Compromise · Credential Dumping Guide · Backup Security and Immutable Backup 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 14 November 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.