
Restoring from backups reduces pressure to pay a ransom
Ransomware operators target backups because successful recovery reduces their leverage. MITRE ATT&CK tracks this as Inhibit System Recovery (T1490). Examples include deleting shadow copies and backup catalogs, disabling recovery options, removing ESXi VM snapshots, and turning off cloud backup policies or versioning.
The November 13, 2025 revision of CISA and FBI’s joint Akira ransomware advisory (AA24-109A) describes exploitation of unpatched Veeam Backup & Replication servers (CVE-2023-27532 and CVE-2024-40711). Backup infrastructure was both a target and a point for privilege escalation. The advisory also documents encryption of Nutanix AHV virtual machine disks in a June 2025 incident. A shared management network can expose both hypervisors and backups to the same compromise.
Windows host activity to monitor first
T1490 activity can involve routine Windows tools, so an executable name alone is insufficient. Collect timestamps, accounts, parent processes, and command lines from Sysmon Event ID 1 and Windows Security Event ID 4688 process creation records. Review the Windows audit policy to confirm it includes command lines in Event 4688.
- Check for unexpected deletion or modification of shadow copies or backup catalogs.
- Verify that changes to recovery settings or stops to backup services were authorized.
- Correlate the events with administrator sign-ins, remote access, and large-scale file changes around the same time.
Legitimate backup software also removes old shadow copies under retention policies. Collect alerts for the first two weeks or so and tune false positives using scheduled backup times, service accounts, and execution paths. Obtain approval from the operations owner before taking any action that could significantly affect recovery.
Protecting the backup server itself
If you use Veeam, start by verifying that you have addressed the two vulnerabilities in the Akira advisory.
| CVE | Details | Mitigation |
|---|---|---|
| CVE-2023-27532 | Vulnerability in Veeam.Backup.Service.exe (default TCP port 9401). CVSS 7.5. | v12: 12.0.0.1420 P20230223 or later. v11a: 11.0.1.1261 P20230227 or later (Veeam KB4424). |
| CVE-2024-40711 | Deserialization of untrusted data can lead to unauthenticated remote code execution. CVSS 9.8. | 12.2.0.334 or later (Veeam KB4649) |
For a single-server setup without remote components, KB4424 recommends blocking external TCP 9401 access at the backup server’s firewall until you can apply the patch. Keep the backup server separate from the business Active Directory domain to reduce the impact of a compromised domain admin account. Limit management ports to a dedicated backup network and require MFA for console access.
Keep a copy that cannot be deleted
CISA’s #StopRansomware Guide recommends encrypted, offline backups of critical data and regular disaster-recovery exercises to verify availability and integrity. Many ransomware variants target accessible backups for deletion or encryption. The guide also discusses immutable cloud storage, including potential regulatory conflicts and the cost of misconfiguration.
These are the questions we ask when reviewing a backup configuration.
- Is there a copy that production accounts cannot delete? Options include Object Lock, tape, and storage under a separate account.
- Are backup administrator accounts separate from business-domain accounts?
- Is the retention period longer than the attacker’s dwell time? If encryption starts after several weeks of access, recent copies may all be compromised.
- Have you tested a full restore?
Restore testing is often where problems surface. Backup jobs may report success daily, yet the restore can fail because its encryption keys or runbooks were locked along with a file server in the same domain. Record exercise dates and restore times so management has evidence for recovery estimates during an incident.
References
- Inhibit System Recovery, Technique T1490, MITRE ATT&CK
- #StopRansomware: Akira Ransomware (AA24-109A), CISA and partners, revised November 13, 2025
- #StopRansomware Guide, CISA
- KB4424: CVE-2023-27532, Veeam
- KB4649: Veeam Security Bulletin (September 2024), Veeam

