CyberKit

Threat intel / Actors and campaigns

SafePay ransomware: FBI and CISA count more than 600 victims

A joint US, German and UK advisory says SafePay has hit at least 600 organizations since August 2024, getting in through VPNs and stolen passwords and wiping backups before it encrypts.

High severity. Active. Moderate confidence. First reported 20 Oct 2026, last activity 20 Oct 2026. Briefing updated 22 Oct 2026.

AI-written summaries of public reporting, each checked against at least two sources from different publishers. Check the sources before you act. Last refreshed 2026-11-18 14:09 UTC. How this is made.

What is not settled: CISA's and IC3's pages could not be opened during this refresh; this briefing is built from search excerpts that quote the advisory and from The Record and BleepingComputer coverage. The specific CVEs the advisory lists are left out until they can be read from the advisory itself. The 600 figure counts victims across sectors, not 600 critical infrastructure operators as some headlines put it, and leak-site counts miss victims who paid.

In plain words

What happened

SafePay is a ransomware gang: it breaks into a company, copies its files, locks them, and threatens to publish the copies unless the company pays. US, German and UK agencies issued a joint warning about it on 20 October.

Who is behind it

The SafePay ransomware operators. The advisory calls them among the most active ransomware groups of 2026.

What they want

Money: a ransom it sets as a share of the victim's revenue, paid in cryptocurrency.

What they did

Since August 2024 the group has hit at least 600 organizations in North America, South America, Europe and Australia. It gets in with stolen or guessed passwords, phishing, or holes in VPNs and firewalls, then deletes backups so the victim cannot recover without paying. Staff also phone victims to push them.

Who is at risk

Organizations with VPN or firewall logins that lack multi-factor sign-in, unpatched internet-facing security devices, or backups that can be reached and erased from the main network.

What to do

  • Turn on multi-factor sign-in for every VPN and remote access account.
  • Patch firewalls, VPNs and other internet-facing devices first.
  • Keep an offline copy of your backups and test that you can restore from it.
The technical version, for hunting and patching

What happened

#StopRansomware advisory AA26-293A, released 20 October by the FBI, CISA, the US Secret Service, Germany's Landeskriminalamt Rheinland-Pfalz, the UK National Crime Agency and North West Regional Organised Crime Unit, profiles SafePay and lists its TTPs and indicators.

Who is behind it

SafePay, active since August 2024. Not tracked by MITRE ATT&CK. The Record notes claimed victims including Microlise and Conduent.

What they want

Double extortion: encryption plus leak-site publication, with ransom demands scaled to victim revenue.

What they did

Initial access through compromised or brute-forced credentials, phishing, and exploitation of internet-facing security devices, often VPN services, with connections from Mullvad VPN addresses. Inside, actors take over accounts, use built-in admin tools, disable security software, stop the Volume Shadow Copy Service and factory-reset NAS devices holding backups, then encrypt with a hybrid scheme and steer victims to a Tor chat portal.

Who is at risk

Edge-device and VPN-heavy environments with password-only remote access, flat access to backup storage, and weak alerting on security tool tampering.

What to do

  • Patch the edge devices named in AA26-293A and enforce phishing-resistant MFA on remote access.
  • Review VPN logs for logins from Mullvad and other commercial VPN ranges, and for new or reactivated accounts.
  • Isolate backup storage and NAS management from domain credentials, and alert on vssadmin, shadow copy service stops and NAS resets.
  • Load the advisory's IOCs and ATT&CK mappings into detections rather than copying them by hand.

Actors

  • SafePay

ATT&CK techniques

Sectors: Multiple. Regions: Global.

Open next

Sources

Revision history

  • 2026-10-22: First published.

Newer: Plex2Shell: four Plex Media Server bugs chained into server takeover. Older: Zeabur breached twice, reads 3.2 million customer secrets, shuts down.