Small-business owners, a ransomware campaign called SafePay has expanded across industries, with more than 600 victims worldwide, according to a joint advisory from CISA and the FBI. The advisory AA26-293A explains how SafePay operates and, crucially, what defenders can do to stop it before it starts encrypting files.
What happened
The CISA/FBI joint advisory notes that SafePay has been one of the more active ransomware groups in 2026, impacting hundreds of organizations across multiple critical infrastructure sectors in the Americas, Europe, and Australia. The advisory provides observed tactics, techniques, and procedures (TTPs), indicators of compromise (IOCs), and recommended mitigations to help network defenders respond quickly.
In short, SafePay campaigns typically rely on common initial access methods and human factors—like phishing or compromised credentials—to gain a foothold. Once inside, the attackers encrypt data and demand a ransom. The key message from the advisory is clear: standard defense gaps (identity, patching, and backups) can turn a breach into a crippling outage for a business.
For readers who want to read the official guidance, see the #StopRansomware: SafePay Ransomware advisory and the accompanying CISA/FBI communications.
Why it matters
- Small and midsize organizations are increasingly targeted. A single foothold can lead to extended downtime and data loss without the right controls in place.
- Ransomware is still very much about access control, not just encryption. Weak identity practices and unpatched systems create easy inroads for attackers.
- Defensive actions don’t require heroic budgets—quick wins can dramatically reduce risk if applied now.
Three defenses that would have stopped SafePay (and how to test them today)
These fixes pair with the safeguards the SafePay advisory recommends. Each defense is paired with a practical, under-15-minute check or action you can perform now.
Defense 1: Strengthen identity and access to stop initial access
What to do
- Enable MFA for all users. In Microsoft 365 or your identity provider, require multi-factor authentication for every account. This makes credential theft far less effective.
- Consider phishing-resistant MFA (FIDO2) where possible, and block legacy authentication that doesn’t support MFA.
- Limit privileged access. Review admin accounts, enable Just-in-Time (JIT) access where possible, and require MFA for admin sign-ins.
How to test quickly
- In your admin portal, verify that all user accounts have MFA enforced and that no admin accounts are exempt from MFA.
- Attempt a quick login with a test user to confirm MFA prompts appear for every sign-in.
Why this matters: MFA is one of the most effective, fast wins against credential-based intrusions that many ransomware operators use as a first step. See the official advisory for deeper guidance on protecting identities.
Defense 2: Patch, segment, and control remote access
What to do
- Patch known exploited vulnerabilities. Check the CISA Known Exploited Vulnerabilities catalog and apply patches to anything listed as known to be exploited.
- Harden remote access. If you allow remote access (VPN, RDP, or remote management), ensure it requires MFA and is not exposed directly to the internet. Prefer VPN with MFA and network segmentation to limit lateral movement.
- Reduce the attack surface. Disable unused services and close unnecessary ports, especially those that face the internet (for example, blocking inbound RDP from the public internet).
How to test quickly
- Go to the KEV catalog and confirm you have patches for any items listed for systems in your environment.
- Review firewall rules: block inbound 3389 (RDP) from the internet in your firewall or router, and require VPN with MFA for any remote access.
Why this matters: Exploiting unpatched vulnerabilities and exposed remote access is a common path to ransomware. The SafePay advisory emphasizes mitigations that directly address these gaps, and practical tests help you validate your defenses.
Defense 3: Protect backups and rehearse incident response
What to do
- Backups should be offline or air-gapped and tested regularly. Ensure you can restore from offline backups quickly if primary systems are encrypted.
- Document and rehearse your incident response plan. Run a tabletop exercise at least quarterly to improve detection, containment, and recovery workflows.
- Segment networks to limit the spread. Ensure critical systems can be isolated if an incident occurs, and that backups cannot be accessed by systems that could be compromised.
How to test quickly
- Run a test restore from your offline backup to a sandbox environment to verify data integrity and restore time.
- Review your IR playbook in 30 minutes and ensure roles, contacts, and runbooks are up to date.
Why this matters: Even with strong prevention, breaches can occur. Ready backups and a practiced response dramatically reduce downtime, data loss, and recovery costs.
Final thought
Ransomware campaigns like SafePay show that attackers keep refining their approach, but solid basics—strong identity controls, timely patching, and reliable backups—remain your best defense. Start with one quick win this week (MFA for all users, a KEV-driven patching check, or a quick backup restore test) and build momentum from there. If you want a quick how-to, I’ll be covering concrete, hands-on steps in future posts—subscribe for updates and stay prepared.
