Rhysida
Aliases: Rhysida ransomware
Source profile review date: 2026-06-01
Added to the source registry: 2023-06-05 · Source snapshot: 2026-09-15
Source metadata is not independently verified. The registry date is not necessarily the first attack date. Source synopses are translated automatically where needed; the feed may contain outdated assessments.
Research status: Existing researched dossier
Locally generated translation; linguistic review is still pending.
Executive summary
Rhysida is a RaaS operation that hits targets of opportunity and often uses VPN- access with valid credentials, RDP, PowerShell and log removal.
Rhysida is relevant to organisations with weak MFA, external remote services and insufficient logging. CISA describes the use of valid VPN-credentials, living-off-the-country, RDP, PowerShell and attempts to erase Windows Event Logs.
Latest five known victim claims
Loading stored claims…
These are public claims attributed to the group, not independently confirmed breaches. Dates indicate publication or discovery, not necessarily the attack date.
Management summary
Rhysida is a ransomware-as-a-service operation that according to CISA, FBI and MS-ISAC mainly targets or opportunity in among others education, care, production, IT and government. For visitors, Rhysida is important because the attack often starts with something very recognizable: valid VPN- access without sufficient MFA or with compromised credentials. Then follow live-off-the-country, RDP, PowerShell, privilege usage and eventually encryption and extortion.
The operational lesson is immediately applicable. An organization that does not monitor external VPN- access, RDP and PowerShell tightly gives Rhysida-like actors the space to behave as an administrator. When log removal is discovered afterwards, the reconstruction is difficult and the actor may have already been at sensitive data.
Rhysida should not be seen as just a ransomwarebinary. It is a chain around valid access, lateral movement, exploration, log manipulation and impact. Anyone who wants to arm himself should especially avoid that a valid account can grow uncontrolled into servers and sensitive data.
Grouping and development
Rhysida is described in public sources as RaaS operation. Affiliates can use tooling and infrastructure in exchange for part of the proceeds. This means that incidents under the same name may have technical differences. Therefore, the profile should keep both common patterns and concrete IOC disregarded.
CISA mentions similarities between Rhysida activity and Vice Society activity, which is relevant because some organisations in education and public sector have previously been targeted by Vice Society-like practices: opportunistic access, data diode, printing through publication and use of existing tools instead of completely proprietary malware.
In 2025, the advisory was supplemented with Gootloader as possible initial access in some Rhysida cases. This makes it clear that initial access can shift. Therefore, the permanent defense points are MFA, detection of loader activity, control of remote services and view on lateral movement.
Attack pattern from public cases
CISA describes that Rhysida-actors use external remote services and authenticate with valid credentials on internal VPN- access points. This is a concrete risk for organizations that are not standardized to MFA, where old accounts remain active or where compromised passwords are not detected quickly.
After access use Rhysida actors living-off-the-country techniques. RDP supports lateral movement, PowerShell can provide discovery and execution, and standard Windows commands can retrieve domain information. For detection, command lines, parent-child processes and RDP- sources are more important than malware files only.
A striking artifact is to clear Windows Event Logs with wevtutil.exe. That's a strong indicator that the actor tries to remove traces. Monitor clearing of System, Application and Security logs as high-risk event, especially when following VPN-login, privilege change or RDP-activity.
Rhysida encryption is associated in the advisory with a Windows 64-bit PE ransomware application that can be injected into processes. Detection on process injection, unusual execution pathways and rapid file changes is therefore relevant, but prevention should be earlier when accessing and lateral movement.
Known IOCs and artifacts
Wevtutil.exe-use for erasing Windows Event Logs is a concrete behavioral indicator from the CISA-advisory. A legitimate admin command here becomes an incident indicator due to timing, account and context.
Valid VPN-credentials without MFA are not IOC in a classic sense, but they are a primary access category. Login from unknown ASNceditors, new devices, impossible travel behaviour or account use outside working hours should be treated as high risk.
RDP- sessions between servers, PowerShell activity, domain exploration and process injection together form a practical detection image. A single single hit can be administrative; the combination after suspicious remote login is strong.
Victim pattern and lessons
Rhysida hits sectors where availability and confidentiality weigh heavily: education, care, government, production and IT. This pattern fits into opportunistic attacks in which the actor seeks organizations that are quickly under pressure when data or systems are not available.
The lesson for schools, healthcare institutions and public organisations is that remote access is often the weakest link. Many environments need external access, but not always mature device control, MFA-hardening and central logging. Rhysida makes this organisational necessity an attack path.
A second lesson is that log retention is part of resilience. If local Windows logs are erased and there is no central SIEM- or EDR- copy, the organization loses sight on timeline and scope.
How to arm yourself against Rhysida
Force MFA on all VPN and remote access routes, remove dormant accounts and monitor new MFA- methods. Combine this with password check for leaked credentials and alerts on login from unknown infrastructure.
Limit RDP to management networks and jump hosts. Log RDP-source, target, account and duration centrally. Do not let servers free of charge between RDP .
Monitor wevtutil.exe and clearing Windows Event Logs. Send logs centrally so that an actor can erase local tracks without destroying the central reconstruction.
Make PowerShell visible with script block logging, constrained language where appropriate and EDR- detection on suspicious command lines. Rhysida uses normal Windows means; the defense must therefore understand behavior, not just blocking files.
Indicators of compromise (IOCs)
Indicators are historical observations, not proof of a current infection. Validate source, age and context before hunting or blocking; legitimate administrative tools can produce false positives.
| Type | Value | Source | Context |
|---|---|---|---|
| command | wevtutil.exe clearing Windows Event Logs | CISA AA23-319A | Rhysida actors used wevtutil.exe to clear System, Application and Security logs. |
| access | valid VPN credentials without MFA | CISA AA23-319A | Observed initial access route via external remote services. |
| tooling | PowerShell | CISA AA23-319A | Living-off-the-country execution and administration. |
| tooling | RDP lateral movement | CISA AA23-319A | Remote Desktop Protocol used for lateral movement. |
| malware | Gootloader initial access in some incidents | CISA AA23-319A update | CISA update notes Gootloader use at times for initial access. |
Sources
Evidence and limitations
Attribution describes the source assessment, not a verified identity. A leak-site listing alone does not prove encryption, data theft, a particular vulnerability or an affiliate relationship. Missing information is left explicit.