When ransomware encrypts your backup files
Ransomware can reach backup repositories through compromised administrator accounts, mapped network shares, synchronised cloud folders, or agents running on the infected computer. Recovery copies may be encrypted, quarantined, or made unavailable alongside the original files.
For Australian households and small organisations, the route often starts with familiar technology. A Melbourne office laptop may sync work files to Microsoft 365, while a Sydney home computer uses Google Workspace and a portable drive; a Perth worker may reach a shared server over the same home Wi-Fi used for banking.
Backup products store snapshots, version history, cloud retention, and offline disks. Ransomware may not destroy every layer, but it can target credentials or connections that expose them. Synchronised folders are copies, not immutable backups, because encrypted changes can propagate. A console reporting “successful” does not prove a restore will work.
Use the first hours to limit further encryption and preserve options. Do not reconnect drives, restart repeatedly, delete samples, or try random recovery software on the only copies.
Isolate the infected device
Disconnect the affected computer from Wi-Fi and Ethernet, unplug removable media, and stop backup or sync clients still writing to a shared repository. Isolate an affected business server rather than shutting down the network blindly. For a screen-locking incident, a step-by-step ransomware cleanup guide offers a useful containment sequence.
Photograph the ransom note and record what was visible before isolation. Keep the device in the state your incident adviser recommends; forced restarts can erase volatile evidence. Reconnect drives only through a clean, isolated workflow.
Determine what the backup damage means
Encrypted, deleted, and unavailable backups need different responses. From a clean device, inspect the backup console, job history, encryption status, and snapshots. Identify the last-known-good restore point and whether the repository, backup account, or sync connection was reached.
Cloud version history and recycle-bin retention may hold usable copies. Do not assume a file extension or ransom note identifies the variant. Record affected folders and keep encrypted samples. This is common in Australian workplaces using Microsoft 365 or Google Workspace, where one compromised sync identity can publish encrypted changes across devices.
Preserve evidence and coordinate a response
Create a timeline of detection, isolation, accounts used, and attacker contact. Preserve endpoint, identity-provider, backup-console, router, and email logs. An encrypted sample can help specialists identify the family and locate a trustworthy decryptor; altering it can reduce recovery chances.
Notify the IT provider, cyber insurer, affected services, and internal leaders. Australian businesses can report through ReportCyber and seek guidance from the Australian Signals Directorate’s Australian Cyber Security Centre; police can receive the ransom note and payment details. Local managed-service providers can help contain the incident.
Remove the malware before restoring anything
Close the attack path before restoring. From a known-clean device, reset passwords for the backup console, cloud tenant, email, remote-access tools, and domain accounts; revoke sessions and multifactor tokens; remove unauthorised forwarding rules, OAuth applications, and scheduled tasks. Patch and scan, or rebuild, affected systems.
If encrypted files sit inside compressed archives, keep the archives intact and test any decryptor on a copy. This Phobos archive recovery advice explains why archive structure, password protection, and file signatures matter. Use reputable security sources, verify the publisher, and never overwrite original evidence.
Restore data without repeating the compromise
Make read-only copies of the damaged repository and record available restore points. Restore into a quarantined virtual machine or isolated network, not directly onto the infected laptop. Test a small sample, then recover identity and finance records, source code, customer files, and configuration in a safe dependency order.
Validate restored files against known-good hashes, open them with trusted applications, and check for macros, altered scripts, or unexpected executables. If no clean copy exists, preserve the encrypted backup and seek specialist advice. Paying does not guarantee a key, and deleting files can destroy evidence.
Recover accounts and reduce recurrence
Attackers often return through stolen credentials and remote-management tools. Review cloud and backup accounts, enforce phishing-resistant multifactor authentication where supported, remove stale administrators, and reserve an emergency administrator account for recovery. Confirm mailbox rules, sharing links, API credentials, and recovery contacts are unchanged.
After restoration, document the incident and assign corrective actions. Keep critical recovery information offline or separately protected; never store the only decryption key beside the files it protects. Immediate priorities include:
- Disconnect affected devices and external drives before reconnecting them.
- Preserve the ransom note, logs, and an encrypted sample for analysis.
- Change passwords from a clean device and revoke active sessions.
- Confirm that offline, immutable, or versioned recovery copies exist.
- Test a restore in isolation and validate file integrity.
- Report the incident to the insurer, IT provider, and appropriate authorities.
Report the incident and build resilience
Australian privacy law may apply alongside sector rules. If personal information is affected and there are reasonable grounds to believe it could cause serious harm, assess the notifiable-data-breach requirements under the Privacy Act 1988, including notification to the Office of the Australian Information Commissioner and affected people. A ransom payment does not remove those obligations.
Critical infrastructure organisations should follow applicable reporting and resilience duties, including those connected with the Critical Infrastructure Act 2018 and Security of Critical Infrastructure Act 2018. Use the Australian Signals Directorate’s Essential Eight as a control baseline, and check cyber-insurance terms for notification deadlines. A resilient design follows the 3-2-1 pattern, with three copies, two storage types, and one offline or immutable copy.
A compact comparison separates a damaged repository from a reachable one:
| What you observe |
Likely meaning |
Safer next action |
| Recent backup jobs show encrypted files |
The repository or its connection was exposed |
Freeze writes, preserve logs, and investigate access |
| A clean snapshot is still listed |
A usable recovery point may exist |
Restore a copy in an isolated environment |
| Cloud files have earlier versions |
Sync credentials may have been abused |
Inspect version history and revoke sessions |
| No usable copy or key is found |
Recovery may require specialist decryptor work |
Keep encrypted evidence and report the incident |