On 20 October, CISA, the FBI, the US Secret Service and international partners published a joint advisory on the SafePay ransomware group. The advisory, AA26-293A, calls SafePay “one of the most active ransomware groups”. It has hit at least 600 organisations since August 2024, across North America, South America, Europe and Australia.
What happened
The advisory draws on investigations by the FBI and German law enforcement. Security Affairs reports that Germany’s Landeskriminalamt Rheinland-Pfalz and two UK law enforcement agencies co-authored it.
SafePay mostly gets in through ordinary weaknesses rather than new ones. CISA lists these routes:
- exposed or stolen credentials
- guessing passwords by brute force
- abuse of VPN access, including from IP addresses linked to the Mullvad VPN service
- phishing
- automated exploitation of known flaws in edge devices and other internet-facing systems.
The Record lists some of the flaws named: CVE-2020-3259, CVE-2023-20269, CVE-2023-27532, CVE-2024-40711 and CVE-2024-40766. Security Affairs describes these as Cisco VPN flaws from 2020 and 2023, a Veeam flaw and a SonicWall access control issue. All of them have had fixes available for some time.
Once inside, the group takes over existing accounts or creates new ones. It uses legitimate administration and remote access tools to move around and to switch off security software. It copies data out before encrypting systems. CISA says it also deletes shadow copies and resets network storage that holds backups, to make recovery harder. Victims are pressed to pay with a leak site and, sometimes, phone calls.
Several victims were themselves suppliers to many other organisations. Infosecurity Magazine reports that SafePay is believed to be behind the November 2024 attack on Conduent. The Record also names Ingram Micro and Microlise among the group’s claimed victims.
What to do now
The agencies’ advice is familiar, which is the point: the basics are what SafePay exploits. In summary, they recommend that you:
- Patch edge devices first. Prioritise VPNs, firewalls and other internet-facing systems, and fix known exploited vulnerabilities quickly.
- Use multi-factor authentication. Require it on remote access, webmail and accounts that reach critical systems.
- Limit administrative tools and rights. Give them only to the people who need them, and review admin accounts.
- Protect your backups. Keep them offline, encrypted and immutable, and test that you can restore from them.
- Segment your network so that ransomware can’t spread easily.
- Watch for unusual sign-ins, including from Mullvad VPN addresses.
How RiskWitness helps
The advisory is a useful checklist. The value comes from showing that you worked through it, and what you decided. This is how that looks in RiskWitness.
Start from the risk. Add a risk such as “Ransomware encrypts systems and data is published”, or pick it from the risk library. Give it an owner and score it before and after your controls.
Link the controls that matter. Link controls for patching edge devices, multi-factor authentication on remote access, limiting admin rights, offline backups and network segmentation. Record how effective each one is against this risk.
Test them, and record the results. Check that remote access really needs a second factor. Restore something from backup. Confirm your VPN and firewall versions are current. Record each test and its result against the control.
Turn gaps into actions. Where a test fails, add an action with an owner and a due date. Overdue actions show on the dashboard until they’re done.
Know your edge devices. Make sure your VPNs, firewalls and backup servers are on the asset register, each with an owner, and linked to the risk.
Ask the suppliers that matter. Several SafePay victims were suppliers to many others. For critical suppliers, send a questionnaire on these controls and keep their answers as assurance evidence on their record.
Decide what you can’t fix yet. If a control can’t be put right straight away, record a risk acceptance with a reason and an expiry. If the risk is outside your tolerance, a named approver signs it off.
Report it. Take the risk, its controls and the open actions to your next security committee meeting. Then share the PDF report or slide deck with the board.
Every one of these steps is kept in a history that records who did what, and when. Nobody can edit or delete it afterwards. When the board, an auditor, a customer or a regulator asks how you responded to this advisory, the record is ready to show.
Sources
- CISA, FBI and partners release joint cybersecurity advisory on SafePay ransomware, CISA, 20 October 2026
- FBI says SafePay ransomware gang ‘among most active’ with more than 600 victims since 2024, The Record, 20 October 2026
- SafePay has compromised 600 critical infrastructure victims worldwide, CISA warns, Infosecurity Magazine, 21 October 2026
- FBI and CISA warn of SafePay ransomware attacks on 600 organizations, Security Affairs, 22 October 2026