Ransomware is malware that encrypts your files and demands a ransom to restore them. Here's how it works and how to avoid paying (no attack steps).
How it works: a criminal business with divided roles
Classic ransomware encrypts every file it can reach on a device or server and leaves a note: "pay if you want the decryption key." But the real nature of today's threat is less about the technology and more about how it makes money.
In double extortion, attackers exfiltrate data before encrypting. So even if a victim restores from their own backups, a second threat remains: "pay or we publish what we stole." That shift is why "we have backups, so we're fine" no longer holds on its own. On top of that, RaaS (Ransomware-as-a-Service) splits the work — those who build the tooling and those who run the attacks are now different people — which has sharply lowered the barrier to entry.
Main entry routes
Ransomware doesn't appear out of nowhere; it comes in through a predictable set of routes. Blocking them is the first defense.
1. Phishing
via email attachments / links. The most common door. defense = MFA, mail filtering, training
2. Exposed VPN/RDP
weak / no-MFA remote access. defense = require MFA, reduce exposure
3. Unpatched flaws
known vulnerabilities in internet-facing software. defense = patch promptly
A real example we've covered, the mass MOVEit Transfer breach, saw a ransomware group exploit an unpatched vulnerability in internet-facing software and steal large volumes of data before a fix was available — a double-extortion case. It's a good reminder that "an email attachment" is not the only way ransomware gets in.
Ransomware vs typical malware
Ransomware is a kind of malware, but its goal and the moment you notice it are very different (→ what malware is).
| Typical malware (spyware and the like) | Ransomware | |
|---|---|---|
| Goal | Steal information or control the device without being noticed | Stop the business and get a ransom paid |
| When you notice | Often runs unnoticed for a long time | Surfaces suddenly, with encryption and a ransom note |
| Main damage | Data leaks, fraudulent transfers, being used to attack others | Downtime, plus publication of the stolen data |
| What decides the outcome | Detection (EDR) and protecting credentials | Offline backups and keeping attackers out |
Examples: ransomware incidents in Japan
These are Japanese cases covered on this site. Most entry points were internet-facing VPN appliances or stolen credentials.
| Case | Reported entry point | Damage and recovery |
|---|---|---|
| Capcom (2020) | An old VPN appliance that was never decommissioned | Personal data of up to about 390,000 people possibly exposed; recovered from backups without paying |
| Handa Hospital (2021) | An unpatched VPN appliance vulnerability | Backups sat on the same network and were encrypted too; about two months to restore electronic medical records |
| Osaka General Medical Center (2022) | A catering contractor's VPN device | Intrusion came through the contractor; outpatient, surgery and emergency care were restricted; just over two months to full recovery |
| KADOKAWA (2024) | Credentials stolen by phishing, per the company's explanation | Many group services down for a long period; personal data of about 250,000 people leaked |
| Medica Shuppan (2026) | Intrusion using legitimate account credentials, per the company | About 641,000 people notified as "possibly leaked" |
What they share is how the internet-facing entry points were managed and where the backups lived. How to protect VPN appliances is covered in VPN devices are ransomware's main way in.
Defense: make recovery-without-paying possible
Keep offline / immutable backups (most important)
Backups are what decide recovery. But an always-online, writable backup can be encrypted along with the rest, so keep at least one offline or immutable (tamper-proof) copy, and run restore tests regularly to confirm you can actually get data back. See backup and recovery essentials (3-2-1).
Prevent intrusion: MFA and patching
Require multi-factor authentication (MFA) on the biggest routes (phishing-prone logins and exposed remote access) and patch known vulnerabilities promptly on anything internet-facing. This alone stops a large share of intrusions (→ choosing MFA).
Limit the damage: least privilege and segmentation
So one compromise doesn't encrypt the whole company, keep privileges to the minimum needed and segment the network. Designing so a single compromised machine can't spread everywhere keeps damage local.
Have detection and an 'after we're hit' plan
Even with these defenses, prevention is never perfect. So detect anomalies early and decide in advance — in an incident response plan — who does what (isolate, notify, restore, in that order). Build the ability to contain and restore before anyone panics and pays.
This site's view: don't rely on paying; prepare in advance
On whether to pay, our position is clear: build the ability to not pay, in advance. Paying doesn't guarantee decryption; with double extortion it doesn't stop the leak either; and it funds crime while marking you as a payer who gets targeted again.
So what matters is preparation, not incident response: an offline backup you can restore, plus MFA and patching that keep attackers out. With both in place, ransomware damage stays at the level of an annoying but recoverable incident.
First steps when you notice an infection
Disconnect from the network
Unplug the network cable and turn off Wi-Fi to stop it spreading to other devices and backups. Avoid careless reboots or power-offs, which can erase records investigators need.
Contact your internal responders and outside authorities
In an organization, use the contacts you agreed in advance. Report to the police or your national cybercrime reporting channel, and if personal data may have leaked, check your data-protection authority's reporting rules.
Check for a decryptor and for clean backups
If the ransom note tells you the family, check No More Ransom for a free decryption tool. At the same time, confirm you have backups the attack didn't touch.
How to check your own setup
- List the product names and versions of your internet-facing VPN appliances and firewalls, and check the vendor advisories and the CVE / KEV Lookup for exploited vulnerabilities still present
- Make sure Remote Desktop (RDP, normally port 3389) can't be reached directly from the internet
- Check that VPN and remote-access accounts require multi-factor authentication (MFA), and that no unused accounts remain
- Confirm at least one backup lives somewhere the production credentials can't delete (offline, or with immutability turned on), and actually restore one file from it
"We have backups" no longer means "we're safe"
Backups used to make ransomware harmless. But now that double extortion is the norm, being able to restore is a different problem from preventing data theft. Attackers pull the data out before encrypting and then demand payment "or we publish it." So defense needs both: not just being able to restore (backups) but also keeping attackers from getting in or taking data out (intrusion prevention). The starting point for modern ransomware defense is refusing to stop at "but we have backups."
Sources (primary)
- National Police Agency of Japan, "Ransomware damage prevention measures" (Japanese) — npa.go.jp (what to do when hit, and prevention)
- No More Ransom, "About the project" — nomoreransom.org (free decryption tools)
- CISA, "#StopRansomware Guide" — cisa.gov (offline backups and response checklist)
- Personal Information Protection Commission of Japan, "Responding to leaks" (Japanese) — ppc.go.jp
Read next
- Learn: backup and recovery essentials (the basics of recovering without paying, including the 3-2-1 rule)
- Learn: choosing MFA the right way (block the biggest route in)
- Glossary: what phishing is (cut off the top entry route itself)
- Case: the mass MOVEit Transfer breach (double extortion via an unpatched flaw) · the Capcom ransomware attack (2020) (an old VPN device as the way in; recovered without paying)
- Glossary: what C2 (command-and-control) is (the post-infection channel attackers operate through)
- Glossary: what malware is (an overview of malicious software — ransomware included — and the shared defense)