A backup is meant to be the file you reach for when everything else has gone wrong. But if ransomware encrypts your live files at 10am and your backup system copies those changes at midday, you may have protected a clean copy of the attack rather than your business. So, can ransomware spread through backups? Yes, particularly where backups are constantly connected, poorly protected or never checked.
For a small or midsize business, this can turn a manageable security incident into prolonged downtime. Staff may be unable to access client records, invoices, booking systems or shared documents, while the pressure to pay a ransom grows. The good news is that ransomware-resistant backup planning is practical and achievable when it is designed around recovery, not simply storage capacity.
Can ransomware spread through backups? How it happens
Ransomware does not always need to infect the backup system as a separate target. Often, the damage happens through normal backup activity. A file is encrypted on a laptop, server or cloud-synchronised folder, and the backup software sees that encrypted version as the latest copy. It then backs it up, potentially overwriting or ageing out the healthy version.
This is why a backup that runs frequently is not automatically a safe backup. Frequent copies improve recovery point objectives, meaning you lose less recent work after an incident. However, they can also copy corrupted or encrypted data more quickly. The right answer is not to back up less often, but to retain enough historical versions to restore a file or system from before the attack began.
Ransomware can also reach backups more directly. If a backup drive is permanently attached to a server, mapped as a network drive or available through an administrator account, an attacker may encrypt or delete it along with everything else. Cybercriminals increasingly look for backup consoles, storage repositories and cloud administration portals after gaining access to a network.
A compromised administrator password creates a similar risk. If the same account, password or privileged device manages both your production systems and backup platform, an attacker who takes control of it may be able to change retention rules, disable jobs, delete restore points or encrypt the backup storage itself.
The backup arrangements that create the greatest risk
The most exposed setup is usually a single backup drive attached to the same computer or server it protects. It is inexpensive and may recover from accidental deletion or hardware failure, but it offers limited protection from ransomware. If the device is online and accessible, ransomware may be able to reach it.
Network-attached storage can be a useful part of a professional backup plan, especially for fast local restores. Yet it needs segregation, restricted access and carefully managed credentials. A shared folder that is visible to every user does not qualify as a secure recovery location.
Cloud backups can be highly effective, but “in the cloud” is not a security guarantee. A cloud service with weak account security, broad permissions or short retention periods can still be tampered with. Businesses should understand whether their provider keeps version history, supports immutable copies and requires additional approval before deletions or major configuration changes.
Another common weakness is relying on file synchronisation as if it were backup. Services that sync documents across devices are useful for collaboration, but they can also sync an encrypted or deleted file quickly. Some platforms provide recycle bins and versioning, which helps, but those features must be configured and retained for long enough to be useful during a delayed discovery.
Build backups around recovery, not hope
A sensible approach is often described as the 3-2-1-1-0 principle. It gives business owners a clear standard without requiring them to become backup specialists:
- Keep at least three copies of important data, including the live version.
- Store those copies on two different types of media or storage platforms.
- Keep one copy off site, away from your main premises and primary network.
- Keep one copy offline, air-gapped or immutable so it cannot be altered during an attack.
- Aim for zero backup errors by monitoring jobs and investigating failures promptly.
Not every organisation needs the same technology. A small office may combine encrypted cloud backup with a protected local recovery appliance. A practice handling sensitive client data may need longer retention, stronger access controls and more frequent testing. The principle remains the same: an attacker should not be able to destroy every copy through one compromised device or account.
Immutability is particularly valuable. An immutable backup cannot be changed or deleted for a defined retention period, even by many administrative accounts. It is not a replacement for good security elsewhere, and retention settings must be chosen with care, but it gives a business a protected point from which to recover when other controls fail.
Offline copies offer a related benefit. A backup that is disconnected once the job is complete cannot be encrypted over the network at that moment. The trade-off is that manual handling can be missed, and physical media still needs secure storage and encryption. For many businesses, immutable cloud storage provides a more consistent option, while an offline copy adds another layer for critical data.
Protect the backup system itself
Treat your backup platform as a high-value business system, not an afterthought. Limit access to people who genuinely need it, use separate administrator credentials and enable multi-factor authentication wherever it is available. A standard user account should not have the ability to alter backup schedules or delete recovery points.
Keep backup software, servers and storage devices patched. Attackers often exploit known weaknesses in remote access tools, operating systems or unpatched appliances before moving through a network. Endpoint protection, email filtering and staff awareness training reduce the chance of a ransomware incident, while protected backups reduce the damage if one gets through.
Monitoring also matters. Failed backup jobs, sudden changes in backup size, unexpected deletion requests and disabled protection settings should trigger an alert. A quiet backup failure is dangerous because it can remain hidden until the day you need to restore.
It is also worth separating backup credentials from ordinary Microsoft 365 or network credentials where possible. If a phishing attack captures one password, it should not hand an attacker the keys to every system. Password managers, multi-factor authentication and least-privilege permissions make this separation easier to maintain.
Test restores before an incident forces the issue
A backup is only proven when it restores correctly. Many businesses check that a backup job reports “successful” but have never opened a recovered file, restored a mailbox or tested whether a key application will run on a recovered server.
Restore testing should reflect the systems that keep your business operating. For one organisation, that may mean customer records and accounting data. For another, it may be property management software, school records, design files or a reservation platform. Test a small file restore regularly, then schedule more thorough recovery exercises for critical systems.
During each test, confirm three things: that the data is usable, that the restore point predates the simulated incident, and that the recovery can be completed within a realistic timeframe. Restoring several terabytes over a slow internet connection may be technically possible but commercially unacceptable if your staff are unable to work for days.
Document who makes decisions during an incident, who contacts suppliers and how staff will continue essential work. This is where disaster recovery planning supports the backup strategy. Backups preserve data; a recovery plan helps the business use that data to resume operations safely.
What to do if ransomware may have affected your backups
Do not immediately run more backup jobs or start deleting files. Disconnect affected systems from the network where safe to do so, preserve evidence and seek professional support. Continuing normal synchronisation can overwrite healthy restore points, while rushed clean-up can make investigation harder.
Check backup logs, retention settings and recent administrative activity. Identify the last known clean point, but be cautious: ransomware may have been present before it became visible. Before restoring, remove the cause of the compromise, reset credentials and verify that recovered systems will not simply be encrypted again.
A well-managed backup solution gives you options when an attack occurs. It may not eliminate disruption, but it can change the conversation from “Should we pay?” to “Which clean restore point gets us back to work fastest?”
If you are unsure whether your current backups would withstand ransomware, a focused review of storage, permissions, retention and recovery testing is a practical place to start. Trust PC Expert can help businesses turn backup arrangements into a dependable recovery plan, so an incident does not have to become a business-ending event.
