Ransomware: the intrusion before the encryption and how to recover

Modern ransomware is a human-operated intrusion: initial access, credential theft, lateral movement, backup destruction, data theft, then encryption. The signals at each stage, the controls that break the chain, and a recovery plan built on tested backups.

Lesson 4 of 18 · 14 min read · practice only with authorization

Diagram

Stages of a human-operated ransomware attack

Follow the path. One example at a time.

Step 1 of 4

Access

Phished credentials, exposed RDP or VPN without MFA, or an unpatched edge device.

Illustration: Access
# Access
# Phished credentials, exposed RDP or VPN without MFA, or
# an unpatched edge device.

The example on the open step is one illustration, or the fix you can paste into an application you own.

What this page is made of

3 pieces. Each one says what fails, who is affected, what you would notice, and what you change.

  1. Initial access

    What fails
    Most incidents start with remote access lacking MFA or an unpatched edge appliance.
    Who is affected
    The whole organization.
    What you would notice
    VPN or RDP sign-ins without MFA; edge CVEs in KEV.
    What you change
    Enforce MFA and patch CISA KEV entries quickly.
  2. Backup destruction

    What fails
    Operators delete shadow copies and backups first.
    Who is affected
    Recovery.
    What you would notice
    vssadmin delete shadows, backup retention changes.
    What you change
    Immutable backups with separate credentials, and alerts on deletion commands.
  3. Data theft

    What fails
    Most groups steal data before encrypting for extra leverage.
    Who is affected
    Customers and staff whose data is taken.
    What you would notice
    Large uploads to file-sharing services before encryption.
    What you change
    Egress monitoring and DLP on sensitive stores.

Recovery order

Recovery follows dependencies: identity first, then core infrastructure, then business systems. Rebuild domain controllers or restore them from known-good backups, reset privileged credentials (including krbtgt twice), then restore applications.

  • Contain: isolate, preserve evidence, stop spread
  • Identity: rebuild or restore DCs, reset privileged accounts
  • Infrastructure: DNS, DHCP, virtualization, backup servers
  • Business systems by priority
  • Monitor closely for re-entry

References

CISA’s #StopRansomware guide and the joint advisories on specific groups list initial access methods and indicators. Reporting to national authorities (in the US, CISA or the FBI through IC3) helps others and may help recovery.

Check yourself

Recognition and the fix. Nothing here is a procedure.

1 / 3

vssadmin delete shadows /all runs on a file server at 02:00. What stage is this?

Sibling techniques

Pages at the same depth, plus a lab and a glossary card for this one.

  1. MapMalware fundamentals: families, delivery, persistence, and the responseWhat malware categories describe, how infections usually start, where persistence hides on Windows, Linux, and macOS, and why rebuilding usually beats cleaning.

Practice

  1. LabTerminal mission: A ransom note rule that stops flagging the FAQA loose ransom-note rule fires on finance documents that mention bitcoin. Read a tighter rule that uses a regex, a count, and filesize, measure the difference, and explain each condition.

Glossary

  1. CardRansomwareSystems and backups are encrypted or stolen, and work stops until recovery or payment.