Classification: TLP:CLEAR | Publication Date: 2026-11-21 | Source: ransomware.live leak-site monitoring | Nature of data: Unverified threat-actor claims
RHYSIDA Ransomware Gang: 5 New Leak-Site Listings Targeting Legal & Municipal Sectors
Executive Summary
Between 2026-11-19 and 2026-11-20, the RHYSIDA ransomware operation listed five organizations on its dark web leak site. The listings are heavily concentrated in US professional services — specifically law firms — with one municipal police department in Georgia. Every listing is independently corroborated at the posting level (two crawlers observed the gang's claims), but none of these listings constitute a confirmed breach. They are accusations by a criminal enterprise.
Regardless of whether any individual claim proves true, RHYSIDA's sector selection is itself actionable intelligence: the group is signaling a focus on small-to-mid-size legal practices and local government entities — organizations that typically hold high-value sensitive data (privileged client communications, PII, case files, law enforcement records) while operating lean security programs. Organizations in these sectors should treat this bulletin as a prompt to validate exposure against RHYSIDA's known initial-access playbook, detailed below.
Sourcing & Verification
- Corroboration tier: 5 of 5 listings in this bulletin were independently observed by a second leak-site crawler. 0 listings appear on a single source only. This means we are confident the gang published these claims; it says nothing about whether the underlying intrusions occurred.
- Inclusion reflects the threat actor's claim and is NOT confirmation of a breach. A leak-site posting is an accusation by a criminal actor with financial incentive to exaggerate, fabricate, or recycle data.
- A named organization may dispute the listing, and a denial is likewise not proof the claim is false. Disclosure obligations vary by jurisdiction, sector, and data type, and not every incident is legally reportable. Neither silence nor denial settles the question — only the organization or its regulator can confirm an incident.
- Corrections: Security Arsenal will publish corrections to this bulletin if warranted and welcomes contact from any named organization at security@securityarsenal.com.
Organizations Listed by RHYSIDA (threat-actor claims, unverified)
| Organization | Sector | Country | Date Listed | Tier |
|---|---|---|---|---|
| BK Law Group LLC | Professional Services | US | 2026-11-20 | Multi-source posting |
| Clarkesville Police Department, City of Clarkesville | Government & Defense | GA (US) | 2026-11-20 | Multi-source posting |
| Rudolph F. Jass, Jr., PLLC | Professional Services | US | 2026-11-19 | Multi-source posting |
| Rober & Phillips | Not Found | Unknown | 2026-11-19 | Multi-source posting |
| Smith & Green, Attorneys at Law PLLC | Professional Services | US | 2026-11-19 | Multi-source posting |
Note the pattern: at least three of the five named entities are law practices, and a fourth (Rober & Phillips, sector unclassified in our data) follows a naming convention consistent with a professional-services partnership. This is a deliberate victimology signal, not randomness.
Threat Actor Profile — RHYSIDA
- Aliases: RHYSIDA (self-branded). No widely accepted alias cluster; some tooling overlaps with other post-Conti ecosystem actors, but RHYSIDA operates under its own brand.
- Model: Operates as a closed, centralized ransomware group with RaaS characteristics — it runs a dedicated leak site and handles its own extortion, but does not appear to run a large open affiliate program on the scale of LockBit. This closed structure typically correlates with more deliberate, hands-on intrusions.
- Ransom demands: Historically calibrated to victim revenue, frequently in the low-to-mid six figures USD for SMB professional-services targets, escalating for government entities. Demands are denominated in Monero/Bitcoin with a short initial deadline and escalating leak threats.
- Initial access methods (documented across campaigns):
- Spear phishing with malicious attachments/links leading to loaders and Cobalt Strike deployment
- Exploitation of externally facing services — VPN concentrators and remote access gateways with weak MFA posture
- RDP exposure — brute force or valid-account access where MFA is absent
- Valid credentials acquired from access brokers
- Extortion model: Classic double extortion — data exfiltration precedes encryption; victims are threatened with publication of stolen data on the gang's .onion leak site if ransom is unpaid.
- Dwell time: Observed dwell times in RHYSIDA intrusions are typically short — days to roughly two weeks — consistent with a smash-and-grab model against smaller targets rather than long-dwell espionage-style operations. This compresses the defender's detection window significantly and makes pre-encryption telemetry (staging, shadow copy deletion, mass file access) the critical tripwire.
- Defense-evasion hallmarks: Volume Shadow Copy deletion via
vssadmin/wmic, disabling of recovery options withbcdedit, PsExec/WMI for lateral distribution of the payload, and scheduled tasks for persistence and execution.
Current Campaign Analysis
Sector targeting
The five listings break down as: 3× Professional Services (all identifiable as law firms), 1× Government & Defense (municipal police department), 1× unclassified. Legal-sector concentration matters: law firms aggregate their clients' most sensitive documents — M&A materials, litigation strategy, PII, PHI in injury practices — making them high-leverage extortion targets. Municipal police departments hold investigative records and citizen PII, and historically face budget-constrained security programs and intense public pressure to resolve incidents quietly.
Geographic concentration
All listings with identifiable geography are United States, with one listing specifically in Georgia. This aligns with RHYSIDA's long-standing US-centric victimology.
Victim profile
Based on the named entities' sectors and apparent scale, this wave skews toward small-to-mid-size organizations — boutique-to-regional law practices and a small-city police department. Estimated revenue/operating scale for such entities typically falls in the $1M–$25M range. This is consistent with RHYSIDA's preference for targets large enough to pay but small enough to lack 24/7 SOC coverage and mature backup/DR programs.
Posting frequency & escalation
Five listings in a 48-hour window (2026-11-19 through 2026-11-20) represents a burst pattern. For a closed group of RHYSIDA's size, batch-posting multiple victims at once often indicates either (a) a completed intrusion cycle being monetized simultaneously, or (b) an intimidation cadence designed to pressure outstanding negotiations. Watch for follow-on postings in the next 7–14 days.
CVE linkage — hypothesis only
We have no evidence linking any specific CVE to any specific named listing above. However, at the sector level, RHYSIDA's documented reliance on phishing and exploitation of perimeter/remote-access infrastructure makes the following CISA KEV entries — all confirmed as ransomware-exploited — directly relevant exposure hypotheses for organizations matching this campaign's victim profile:
- CVE-2026-50751 (Check Point Security Gateway — improper authentication in IKEv1 key exchange): perimeter VPN exposure is squarely in RHYSIDA's initial-access playbook. If your gateway is unpatched, treat that as a standing invitation.
- CVE-2026-20316 (Cisco Secure FMC — hard-coded password): management-plane compromise enables full network traversal and policy manipulation.
- CVE-2026-59310 (VMware vCenter — path traversal): virtualization-plane access is the highest-value lateral target pre-encryption; compromising vCenter enables mass hypervisor-level encryption.
- CVE-2026-63077 (JetBrains TeamCity — deserialization/RCE): build servers are increasingly used as entry points into otherwise segmented environments.
- CVE-2026-48027 (Nx Console — embedded malicious code): supply-chain/developer-toolchain exposure; relevant to phishing-adjacent delivery chains.
Action: reconcile these CVEs against your asset inventory this week. These are confirmed ransomware-exploited per CISA KEV — patch status on these is not a theoretical exercise.
Detection Engineering
The following rules target RHYSIDA's documented TTPs: perimeter/VPN exploitation, phishing-driven execution, PsExec/WMI lateral movement, and pre-encryption staging (shadow copy deletion, recovery tampering, mass exfil staging).
---
title: RHYSIDA Pre-Encryption Defense Evasion - Shadow Copy and Recovery Tampering
id: 7f3a1c2e-9b41-4e6a-a1d0-rhysida00001
status: production
description: Detects deletion of Volume Shadow Copies and boot recovery tampering consistent with RHYSIDA pre-encryption behavior (vssadmin, wmic, bcdedit)
author: Security Arsenal Threat Intelligence
references:
- https://securityarsenal.com/darkside
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
date: 2026/11/21
modified: 2026/11/21
tags:
- attack.impact
- attack.t1490
- attack.t1562.001
logsource:
category: process_creation
product: windows
level: critical
detection:
selection_img:
Image|endswith:
- '\vssadmin.exe'
- '\wmic.exe'
- '\bcdedit.exe'
selection_cli:
CommandLine|contains:
- 'delete shadows'
- 'shadowcopy delete'
- 'resize shadowstorage'
- 'recoveryenabled no'
- 'bootstatuspolicy ignoreallfailures'
condition: selection_img and selection_cli
falsepositives:
- Legitimate backup administrators (rare; verify change tickets)
---
title: RHYSIDA Lateral Movement - PsExec-Style Remote Service Creation
id: 7f3a1c2e-9b41-4e6a-a1d0-rhysida00002
status: production
description: Detects remote service installation consistent with PsExec / PsExec-clone lateral movement used by RHYSIDA to distribute ransomware payloads
author: Security Arsenal Threat Intelligence
date: 2026/11/21
modified: 2026/11/21
tags:
- attack.lateral-movement
- attack.t1569.002
- attack.t1021.002
logsource:
product: windows
service: system
detection:
selection_eventid:
EventID: 7045
selection_svc:
ServiceName|contains:
- 'PSEXESVC'
- 'RemComSvc'
selection_path:
ImagePath|contains:
- '\ADMIN$\'
- '\PSEXESVC'
condition: selection_eventid and (selection_svc or selection_path)
level: high
falsepositives:
- Enterprise software deployment tools using PsExec-like mechanisms (SCCM alternatives, PDQ)
---
title: RHYSIDA Initial Access - VPN Anomaly Followed by RDP and Office Macro Execution
id: 7f3a1c2e-9b41-4e6a-a1d0-rhysida00003
status: production
description: Detects Office applications spawning scripting or LOLBin child processes — consistent with RHYSIDA phishing-macro execution chains
author: Security Arsenal Threat Intelligence
date: 2026/11/21
modified: 2026/11/21
tags:
- attack.initial-access
- attack.execution
- attack.t1204.002
- attack.t1059
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|endswith:
- '\winword.exe'
- '\excel.exe'
- '\outlook.exe'
- '\powerpnt.exe'
selection_child:
Image|endswith:
- '\powershell.exe'
- '\pwsh.exe'
- '\cmd.exe'
- '\wscript.exe'
- '\cscript.exe'
- '\mshta.exe'
- '\rundll32.exe'
- '\regsvr32.exe'
- '\certutil.exe'
- '\bitsadmin.exe'
condition: selection_parent and selection_child
level: high
falsepositives:
- Legacy line-of-business macro workflows; baseline and exclude known-good templates
The following Microsoft Sentinel query hunts the RHYSIDA pre-ransomware staging window: authentication from VPN perimeter sources followed by anomalous admin-share writes, new service creation, and shadow-copy tampering within a compressed time window — the gang's short-dwell signature.
// RHYSIDA pre-encryption staging hunt: VPN logon -> admin share/service -> VSS tampering within 6h
let window = 6h;
let vpnLogons =
SigninLogs
| where TimeGenerated > ago(7d)
| where AppDisplayName has_any ("VPN", "AnyConnect", "GlobalProtect", "FortiClient")
or IPAddress in (external_data(string) dynamic([])) // substitute known concentrator IPs
| where ResultType == 0
| summarize FirstVpnLogon=min(TimeGenerated) by UserPrincipalName, IPAddress;
let suspiciousHostActivity =
union isfuzzy=true
(SecurityEvent
| where TimeGenerated > ago(7d)
| where EventID in (5145, 7045, 4688)
| extend Detail = case(
EventID == 5145, strcat("AdminShare:", ShareName),
EventID == 7045, strcat("NewService:", ServiceName),
EventID == 4688, strcat("Process:", ProcessName, " | ", CommandLine),
"")
| where Detail has_any ("ADMIN$", "C$", "PSEXESVC")
or (EventID == 4688 and CommandLine has_any ("delete shadows", "recoveryenabled no", "shadowcopy delete"))
| project TimeGenerated, Account, Computer, EventID, Detail),
(DeviceProcessEvents
| where TimeGenerated > ago(7d)
| where ProcessCommandLine has_any ("vssadmin delete shadows", "bcdedit", "wmic shadowcopy")
| extend Account = AccountName, Computer = DeviceName, Detail = ProcessCommandLine
| project TimeGenerated, Account, Computer, Detail);
suspiciousHostActivity
| extend AccountLower = tolower(Account)
| join kind=inner (vpnLogons | extend AccountLower = tolower(split(UserPrincipalName, "@")[0])) on AccountLower
| where TimeGenerated between (FirstVpnLogon .. (FirstVpnLogon + window))
| summarize ActivityCount=count(), Activities=make_list(Detail), Hosts=make_set(Computer)
by AccountLower, IPAddress, FirstVpnLogon
| where ActivityCount >= 2
| sort by ActivityCount desc
The following PowerShell script is a rapid-response triage tool for organizations matching this campaign's profile (legal, municipal). It surfaces the exact artifacts RHYSIDA leaves in its short-dwell window: newly created scheduled tasks, recent shadow-copy manipulation, exposed RDP, and newly created local admins.
# Security Arsenal - RHYSIDA Rapid Triage Script
# Run elevated on suspect hosts or via your EDR's live-response shell.
# Outputs consolidated triage report to C:\IRTriage
$outDir = "C:\IRTriage"
New-Item -ItemType Directory -Path $outDir -Force | Out-Null
$cutoff = (Get-Date).AddDays(-7)
$report = @()
# 1. Scheduled tasks created or modified in last 7 days (persistence / payload staging)
$tasks = Get-ScheduledTask | Where-Object { $_.Date -and ([datetime]$_.Date) -gt $cutoff } |
Select-Object TaskName, TaskPath, Date, Author
$tasks | Export-Csv "$outDir\NewScheduledTasks.csv" -NoTypeInformation
$report += "Scheduled tasks (last 7d): $($tasks.Count)"
# 2. Volume Shadow Copy status (RHYSIDA deletes these pre-encryption)
$shadows = Get-CimInstance Win32_ShadowCopy -ErrorAction SilentlyContinue
$report += "Existing shadow copies: $(@($shadows).Count) <-- ZERO on a server is a red flag"
$shadows | Select-Object ID, InstallDate, VolumeName | Export-Csv "$outDir\ShadowCopies.csv" -NoTypeInformation
# 3. Recent vssadmin/bcdedit execution evidence from Prefetch
$prefetch = Get-ChildItem "C:\Windows\Prefetch" -ErrorAction SilentlyContinue |
Where-Object { $_.Name -match 'VSSADMIN|BCDEDIT|WMIC' -and $_.LastWriteTime -gt $cutoff }
$prefetch | Select-Object Name, LastWriteTime | Export-Csv "$outDir\SuspiciousPrefetch.csv" -NoTypeInformation
$report += "vssadmin/bcdedit/wmic prefetch hits (last 7d): $(@($prefetch).Count)"
# 4. RDP exposure check
$rdpEnabled = (Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections -ErrorAction SilentlyContinue).fDenyTSConnections -eq 0
$nlaEnabled = (Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name UserAuthentication -ErrorAction SilentlyContinue).UserAuthentication -eq 1
$report += "RDP enabled: $rdpEnabled | NLA required: $nlaEnabled"
if ($rdpEnabled -and -not $nlaEnabled) { $report += ">>> WARNING: RDP enabled without NLA - RHYSIDA initial-access risk" }
# 5. Local admin accounts created in last 7 days
$admins = Get-LocalGroupMember -Group "Administrators" -ErrorAction SilentlyContinue
$admins | Select-Object Name, ObjectClass, PrincipalSource | Export-Csv "$outDir\LocalAdmins.csv" -NoTypeInformation
$report += "Local admin members: $(@($admins).Count) - review for unexpected additions"
# 6. Windows Event Log 1102 (log cleared) - anti-forensics indicator
$cleared = Get-WinEvent -FilterHashtable @{LogName='Security'; Id=1102; StartTime=$cutoff} -ErrorAction SilentlyContinue
$report += "Security log clear events (last 7d): $(@($cleared).Count)"
$report | Out-File "$outDir\TriageSummary.txt"
Write-Host "Triage complete. Review $outDir - escalate to IR if shadow copies are missing, unexpected services/tasks exist, or log clears are present."
Incident Response Priorities
T-minus detection checklist (before encryption fires)
RHYSIDA's short dwell time means your window is measured in hours-to-days. In priority order:
- Shadow copy / recovery tampering events (
vssadmin delete shadows,bcdeditrecovery changes) — if you see this on a server, assume detonation is imminent. - New service installations (Event 7045) — especially PSEXESVC or services pointing into
ADMIN$. - Anomalous admin-share writes across multiple hosts from a single account — lateral payload staging.
- Mass file read/archive activity on file servers — data staging prior to exfil (watch for 7-Zip/WinRAR execution on servers that never run them).
- New local admin or service accounts created outside change control.
- EDR/AV tampering events — services stopped, sensors uninstalled, exclusions added.
Assets this gang prioritizes for exfiltration
- Legal-sector: client matter files, privileged correspondence, contracts, settlement documents, HR/PII stores — anything that creates third-party liability pressure on the firm.
- Municipal/police: case and investigative records, citizen PII, personnel files, body-cam metadata repositories.
- Both: backup repositories (targeted for destruction), virtualization management planes (vCenter), and domain controller NTDS.dit for credential theft.
Containment actions — ordered by urgency
- Isolate affected segments at the network layer — do NOT power off hosts (destroys forensic memory); VLAN-ACL isolation first.
- Disable compromised/ suspect accounts and force enterprise-wide credential resets for any account observed in lateral-movement telemetry — assume krbtgt and DA-tier compromise if DC telemetry is implicated; plan a double krbtgt reset.
- Block exfil egress — deny outbound to unknown destinations; inspect for large TLS flows to cloud storage or bulletproof hosting ASNs.
- Snapshot/verify backups NOW — confirm offline/immutable copies are intact and segregated before attackers reach the backup plane.
- Preserve evidence — memory capture and triage collection on patient-zero and any host with VSS-tampering events, before any rebuild.
- Engage IR counsel and your retainer — notification obligations for legal firms and government entities are jurisdiction-specific and clock-driven.
Hardening Recommendations
Immediate (24 hours)
- Patch the perimeter against KEV entries relevant to RHYSIDA's playbook: CVE-2026-50751 (Check Point gateway auth bypass), CVE-2026-20316 (Cisco FMC), CVE-2026-59310 (vCenter). Confirm in your scanner, not on a spreadsheet.
- Enforce MFA on all remote access — VPN, RDP gateways, webmail. RHYSIDA's access vector collapses when MFA is present and enforced without legacy-protocol exceptions.
- Disable RDP from the internet entirely; if internal RDP is required, require NLA and restrict to jump hosts.
- Block Office macro child-process execution via ASR rules — directly breaks the phishing-to-loader chain (see Sigma rule 3 above).
- Deploy the VSS-tampering Sigma rule and Sentinel query from this briefing; test alerting end-to-end.
- Verify one immutable/offline backup copy of critical data is current and restorable.
Short-term (2 weeks)
- Segment backup infrastructure and virtualization management (vCenter/ESXi) onto isolated networks with dedicated admin accounts and no shared credentials with general AD — RHYSIDA's encryption blast radius scales with hypervisor access.
- Implement tiered administration — separate DA-tier credentials from workstation use; enable LAPS and gMSA for service accounts.
- Egress filtering with TLS inspection on server VLANs — servers rarely need arbitrary internet egress; exfil staging dies here.
- Deploy attack-path reduction: disable legacy protocols (NTLMv1, SMBv1), restrict WMI/PsExec to defined management hosts via host firewall policy.
- Legal/municipal-specific: enable Purview/MIP or equivalent classification on matter files and investigative records so exfiltrated-data exposure can be scoped quickly — notification decisions will hinge on this.
- Tabletop a 48-hour-dwell scenario — RHYSIDA's tempo means your IR plan must execute containment steps in hours, not days.
Related Resources
Security Arsenal Incident Response Managed SOC & MDR Services AlertMonitor Threat Detection From The Dark Side Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.