The popular image of ransomware is a single bad click followed by a red screen demanding Bitcoin. That still happens with some commodity strains, but the attacks that shut down hospitals, manufacturers and IT service companies look very different. They are run by organised groups, unfold over days or weeks, and treat encryption as the final act. Understanding the stages before it is what turns ransomware from a disaster you recover from into an intrusion you interrupt.

Myth: ransomware is a piece of malware

Reality: it is a business model. Much of today’s ransomware runs as Ransomware-as-a-Service. A core group develops the encryption software, runs the leak website and handles negotiation. Affiliates carry out the actual intrusions and share the ransom with the developers. Separately, initial access brokers specialise in breaking into organisations and selling that access, for example a working VPN login or a foothold on a server, to whoever pays.

This division of labour matters for defenders. The people who got in may not be the people who encrypt. A “minor” intrusion, such as an infostealer on one laptop or an exposed remote desktop service, can be resold and become a full ransomware incident weeks later.

Myth: it all happens in minutes

Reality: there is usually a window, though it is shrinking. A typical human-operated attack follows a recognisable path:

  1. Initial access: stolen VPN or remote access credentials, an unpatched internet-facing appliance, or a phishing payload.
  2. Establishing control: a remote access tool or command and control implant, often a legitimate remote support product repurposed.
  3. Discovery: mapping the network, finding domain controllers, file servers, backup servers and virtualisation hosts.
  4. Credential theft and privilege escalation: the goal is domain administrator or equivalent, because that unlocks everything else.
  5. Lateral movement to the important systems.
  6. Data theft: copying sensitive files out, often with common file-sync or transfer tools.
  7. Sabotaging recovery: deleting or encrypting backups, removing volume shadow copies, disabling security tools.
  8. Encryption, typically pushed to many machines at once, frequently timed for a weekend, holiday or night.

Industry incident reports have described the time from initial access to encryption falling over the years, in some cases to a matter of days or even hours. Still, steps 2 to 7 generate signals: new remote tools appearing, unusual authentication patterns, admin tools used by unusual accounts, large outbound transfers, backup jobs failing. A SOC that notices any one of them is ahead of the encryption.

Myth: good backups make ransomware harmless

Reality: backups solve one problem, and attackers know it. When organisations got better at restoring from backup, groups adapted with double extortion, popularised around 2019 and 2020. Before encrypting, they steal data. If the victim restores and refuses to pay, the group threatens to publish the data on a leak site. Some groups add further pressure, such as contacting the victim’s customers or launching denial-of-service attacks, sometimes called triple extortion. A few skip encryption entirely and just steal and extort.

Backups also have to survive the attack. Attackers with domain admin rights deliberately look for backup consoles and network-attached backup storage. Backups that are immutable (cannot be altered for a retention period) or offline, with separate credentials not tied to the main directory, are the ones that reliably survive. And a backup nobody has test-restored is a hope, not a plan: restoring hundreds of servers can take far longer than expected.

Myth: encryption is about locking files

Reality: it is engineered for speed and maximum damage. Modern ransomware typically encrypts each file with a fast symmetric key and then protects that key with the attacker’s public key, so only the attacker can unlock it. Some families use intermittent encryption, scrambling only parts of each file, which is enough to make it unusable while finishing much faster. Many groups now target virtualisation hosts directly: encrypting one hypervisor’s virtual disk files can take down dozens of servers in a single action.

Where defenders get the most leverage

Mapping controls to the stages gives a practical priority list:

  • Access: MFA on every remote access path, fast patching of internet-facing appliances, and removing exposed remote desktop services.
  • Control and movement: EDR on all servers as well as laptops, alerts on new remote management tools, and limiting where admin accounts can log in.
  • Credentials: separate admin accounts, protection of credential stores, and watching for credential-dumping behaviour.
  • Exfiltration: alerts on unusually large outbound transfers, especially to file-sharing services, from servers that do not normally send data out.
  • Recovery: immutable or offline backups, separate backup credentials, and rehearsed restores.

Indian organisations also face reporting duties. CERT-In’s 2022 directions require specified incidents, including ransomware, to be reported within six hours of being noticed, and sector regulators may have their own rules. Knowing who makes that call and with what information is part of being ready.

The single most useful reframing is this: the ransom note is not the start of the incident. It is the moment the attacker decided they had finished. Everything the defender can do cheaply happens before that.

Written by the RP Strativa Team.

Leave a Reply

Trending