Threat library

Ransomware: contain damage and plan recovery

Investigate suspected ransomware, preserve recovery options, distinguish encryption from scams and stolen data, and coordinate device, account and file recovery.

Sudden widespread file changes need prompt assessment, especially when accompanied by a ransom note or an installed security product’s finding. Stop ordinary work and preserve the options for recovery. Removing a malicious program, restoring readable files and closing unauthorized access are separate outcomes; progress on one does not settle the others.

This guide helps a Windows PC or Mac owner organize that response. It does not provide a universal decryptor or a do-it-yourself procedure for repairing an organizational network. On work or school equipment, use the established incident contact through a separate trusted device. Use the ransomware glossary for terminology and the beginner flow for immediate triage.

Stop ordinary use and make a containment decision

On a personal device, stop sensitive work, disconnect Wi-Fi and Ethernet, and arrange qualified help. Leave detached backup drives detached. Network disconnection can limit communication and spread, but code already running can continue changing local files. If damage continues, obtain urgent incident-specific advice rather than treating disconnection as a completed repair.

NCSC’s immediate-response guidance explains the tradeoff: shutting down may halt active processes but loses investigative evidence. Its organizational guidance balances containment, safety, investigation and operational impact. It also recommends recording decisions and checking the availability and integrity of backups. Use a qualified responder for that assessment; routine restarts, reinstallations and recovery experiments can complicate it.

For managed equipment, tell IT what changed and when. Do not disconnect shared servers, delete cloud resources or attempt to repair colleagues’ devices without the responsible team’s directions. Use independently verified support details; the ransom note and a browser warning are not trustworthy routes to help.

Establish what actually became inaccessible

Record the affected device, first known time, file locations, changed names or extensions, exact warning and security-product action. Use information already visible rather than opening suspicious programs or repeatedly testing damaged documents. A screenshot or private written record can help a responder understand the event without sending your files to strangers.

ObservationWhat needs assessmentAvoid assuming
A browser page demands payment but local files workPage content, permissions and anything you already didThat the page encrypted the computer
One document fails to open without a wider patternApp, storage, permissions and that file’s historyThat every unreadable file is ransomware
Many files change alongside a ransom note or findingActive damage, affected locations and incident timelineThat renaming extensions will decrypt them
A product blocked a ransomware-related downloadRecorded prevention action and possible executionThat encryption necessarily occurred
A threat claims it stole data without file lockingExposure and the credibility of the claimThat a backup can resolve disclosure

Use pop-up diagnosis for a demand confined to a web page, while preserving any earlier software installation or account exposure. Genuine encryption and a scam message can coexist. A ransom note’s branding or filename alone is not enough to establish a family or an applicable recovery tool.

Separate recovery copies from affected storage

List potential copies privately: disconnected drives, another device, file-version history and cloud recovery features. Record when each was last updated and whether it was connected or accessible during the suspected incident. A recently completed backup can contain already damaged files; its date is useful context, not an integrity guarantee.

Do not attach an independent copy to the affected environment just to browse it. Decide with the responder where it can be inspected and restored safely. Keep the original encrypted or damaged data available; an overwrite, disk-format operation or broad cleanup may remove material useful for later recovery.

NCSC’s malware and ransomware guidance explains why protected offline copies and tested restoration matter. For the practical choices, use ransomware backup planning and personal-file restoration. A synchronized folder is not automatically an independent backup: available versions, retention and access determine the recovery options.

Assess a decryptor without sacrificing originals

No More Ransom’s decryptor catalog lists tools with specific supported threats and linked how-to instructions. Read the relevant manual before downloading or using a solution. The project says malware should be removed first to prevent files being encrypted again. That prerequisite does not establish that your entire incident has been remediated.

A qualified assessment should establish the actual match, required evidence and safe destination. A similar ransom note, guessed family name or filename extension does not guarantee compatibility with a variant. Preserve originals and follow the tool’s documented preparation and copy-handling requirements; do not experiment across your only copy of important data.

Crypto Sheriff is an optional identification service. Its form accepts encrypted files and ransom-demand details, including an optional note file, and requires agreement to its data-provisioning terms. That is an external submission. Consider confidentiality and organizational authorization before using it; encryption does not make every included detail suitable for disclosure. You can discuss a private identification route with your responder instead.

An unavailable or unsuccessful decryptor is not proof that every other recovery route is exhausted. Preserve the case record and copies while considering trusted backups and provider version recovery. Do not accept guaranteed-recovery claims from unsolicited messages, and do not treat a successfully restored sample as proof that the whole data set is intact.

Address access and disclosure alongside file recovery

Write separate questions for the device, accounts and data. What code or access enabled the event? Which other devices or services were reachable? Is there credible evidence of copied information, changed credentials or unauthorized account activity? A readable restored document cannot answer those access questions.

Use account recovery from another trusted device for affected accounts. Prioritize the identity controlling password resets and relevant administrative access. For a stealer-related finding, the exposure investigation helps inventory sessions, app grants and secrets. Record uncertain exposure as uncertain rather than claiming all private data was taken or nothing escaped.

The FBI’s ransomware advice does not support ransom payment and explains that payment does not guarantee recovery. Its reporting routes are for the United States. Elsewhere, use the relevant local authority and trusted incident support. Organizations need their responsible team to assess reporting duties, contractual requirements and disclosure; this guide supplies no universal legal deadline.

Restore in stages and verify the actual outcome

Plan a trusted device or rebuilt environment before restoring wanted data. Keep programs, whole-system images and browser profiles in the scope assessment rather than importing everything automatically. Recovery verification helps record completed remediation and unresolved findings separately from restored files.

Verify a bounded selection of recovered documents in their intended applications before depending on the entire recovery, using the safety checks in file restoration. Do not enable active content or run a recovered installer merely to test readability. Check that the versions are the ones you wanted, document anything missing or unreadable, and keep recovery sources until the result has been assessed. Avoid reconnecting shared or cloud-synchronized environments before the responsible team has addressed continuing access and affected devices.

The completion record should identify containment decisions, assessed systems, completed security actions, recovered versions and remaining exposure questions. “The desktop opens again” is an observation, not the full incident outcome. This article is based on documentation research. No ransomware sample was run, encrypted file uploaded, decryptor tested or recovery success rate measured to prepare it.

Sources & documentation

Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.

MalwareCleanupTools

Guides based on official documentation. About our content · Corrections policy