Glossary

Ransomware: encryption, extortion, and recovery

Understand what ransomware does, why removing it does not decrypt files, and how containment, backups, data theft, and recovery fit together.

Definition

Ransomware is malware that denies access to a device or data, commonly by encrypting files, and is used to demand payment in exchange for purported restoration of access.

Also called: file-encrypting ransomware, crypto-ransomware, locker ransomware

If files are being encrypted now

For a practical incident path, use ransomware containment and recovery planning. It separates the initial evidence, independent copies, decryptor matching and disclosure/access work from the definition below.

Treat sudden widespread file changes accompanied by a ransom note or a confirmed ransomware alert as an incident requiring prompt containment. Stop ordinary work on the affected device and avoid connecting backup drives. Disconnect a personal device from network connections while arranging qualified help.

For a work or school device, contact IT immediately through a separate communication route. Follow its incident response process. CISA’s StopRansomware Guide prioritizes isolating affected systems and preserving evidence. Its organizational response checklist is not a reason to change shared network infrastructure on your own.

Routine restarting, reinstalling, or experimenting with recovery tools can remove evidence or complicate recovery. CISA treats powering down as a fallback when network isolation is impossible, because shutdown loses evidence held in memory. Get incident-specific guidance when that tradeoff matters.

What ransomware changes

Ransomware commonly encrypts files so that their contents cannot be read normally. Other forms lock access to a device. The attacker demands payment while claiming to offer a decryption key or another way to restore access.

Encryption changes the data; it does not merely change the filename. Renaming an affected document or removing an added extension does not undo the encryption. A familiar icon or a normal-looking directory can therefore remain while the file’s contents are unusable.

Not every inaccessible file is ransomware. An application error, damaged storage, or an ordinary permission problem can also stop a file opening. A browser page demanding money may be a scam rather than evidence that local files were encrypted. Look for the actual file changes, the installed security product’s findings, and the incident context.

The payload can be one stage of a larger attack

The ransomware component describes the denial of access. It does not tell you how an attacker first entered, how long access existed, or whether information was taken beforehand.

Microsoft’s ransomware explanation distinguishes automated attacks from intrusions in which people use compromised access to move through an environment and deploy a payload. Removing one malicious file may leave those earlier access paths unresolved.

A Trojan may conceal a malicious payload; a worm may provide replication; an infostealer may expose credentials used in a later intrusion. A ransomware event does not prove that all of those components were involved, but it makes the wider scope a relevant question.

Encryption and data extortion are different harms

Attackers may steal information and threaten to release it as well as encrypting files. Recovering access from a backup addresses availability. It cannot take back a copy already obtained by someone else.

OutcomeThe problem to resolveWhat recovery alone does not establish
Encrypted filesRestore usable data or find an applicable decryptorThat the attacker no longer has access
Locked deviceRegain control of a trustworthy systemThat accounts and other devices are unaffected
Stolen informationAssess exposure and secure affected accessThat restored files erase the disclosure
Continued unauthorized accessRemove the access path and compromised componentsThat deleting the visible ransom note is enough

Data extortion can also occur without ransomware encrypting anything. Keep the actual effects separate rather than using one label to assume what happened. A managed organization needs its incident team to assess the systems, accounts, and information involved.

Removal does not decrypt files

Security software can identify and handle malicious code. Decryption is a different task involving the affected data and, usually, the relevant cryptographic keys or a specific recovery weakness.

Quarantining a ransomware executable does not reverse encryption it already performed. Likewise, recovering a few documents does not establish that the device is trustworthy. Malware explains the broader distinction between cleanup and recovery.

Record the detection, affected file locations, ransom note, and timing. Preserve encrypted originals before attempting a recovery method. A qualified responder can determine which evidence and copies are needed without turning every file into a public submission.

What backups can and cannot provide

For preparation before an incident, the ransomware backup guide covers independent copies, account access, history, deletion controls, and a bounded restore exercise. Offline backups explains a practical removable-drive routine.

A verified backup from before the incident may provide usable data. The important questions are whether that copy is intact, whether it was exposed to the attack, and whether the destination is safe for restoration.

CISA recommends protected backups and testing restoration. A drive attached to the compromised environment can be exposed along with ordinary files. Cloud synchronization is not automatically an independent backup: synchronized changes and the service’s available version history affect what can be recovered.

Do not reconnect backup storage to an actively affected device just to check it. Plan restoration into a clean environment and assess whether the backup includes compromised programs or configurations. Otherwise, data recovery can reintroduce the problem.

Decryption tools have a specific scope

No More Ransom provides recovery resources and decryption tools for supported threats. It explicitly states that not every type of ransomware has a solution.

An applicable tool depends on the actual ransomware and affected data. A tool for one family or variant should not be treated as a universal decryptor. Use the project’s official instructions and qualified assistance to establish a match, and work on preserved copies where the instructions allow. Avoid tools advertised by unexpected messages promising guaranteed recovery.

A ransom demand is not a recovery guarantee

The FBI does not support paying ransom and explains that payment does not guarantee data recovery. A payment also does not establish that copied information was deleted or that an attacker relinquished access.

Seek qualified incident support and use the relevant local reporting route. The FBI’s reporting instructions are for its jurisdiction; organizations elsewhere should use their own applicable channels and response plans.

A resolved incident requires more than removing a note or restoring the desktop. The useful record identifies the compromised access, completed containment and cleanup, verified recovery, and any remaining data exposure. Those outcomes explain what has actually been repaired.

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