Multi-extortion ransomware explained: why backups alone no longer save you

Ransomware now pairs encryption with data theft and pressure on customers. What 2025-26 incidents show, and the controls engineering teams should prioritise.

TechLogHub Engineering Team
April 3, 2026
4 min read
0 views

Share Article

Evolution of Ransomware: Multi‑Extortion Ransomware Attacks

Ransomware used to be an availability problem: files were encrypted, and good backups were the answer. Today most serious ransomware incidents are also data breaches, because attackers steal data before they encrypt anything and then use it as a second, and sometimes third, lever. If you build or run systems that hold customer data or sit in someone else's payment or care pipeline, that shift changes what "resilient" means.

What happened

Extortion tactics have stacked up in layers over the past several years:

  • Single extortion: encrypt systems and sell the decryption key.
  • Double extortion: exfiltrate data first, then encrypt, and threaten to publish the stolen files on a leak site if the victim restores from backup and refuses to pay.
  • Multi- or triple extortion: add more pressure, such as contacting the victim's customers, partners or patients, or threatening regulators' attention and public embarrassment.

Recent data shows the scale. BlackFog's 2025 State of Ransomware report counted 1,174 publicly disclosed ransomware attacks in 2025, a 49% rise on 2024, and estimates that around 86% of attacks are never publicly reported. In healthcare, the Proofpoint and Ponemon Institute 2025 survey of 677 US healthcare IT and security professionals found that 93% of organisations had at least one cyberattack in the past year, and 72% of those hit by attacks such as ransomware, cloud compromise or supply-chain attacks reported disruption to patient care.

Two incidents from early 2026 show how far the damage reaches:

  • University of Mississippi Medical Center (February 2026): a ransomware attack compromised its IT network and its Epic electronic health record platform. UMMC closed 35 clinics statewide and cancelled chemotherapy appointments and elective procedures while hospitals and emergency departments kept operating.
  • BridgePay Network Solutions (6 February 2026): a ransomware attack on the payment gateway disrupted its gateway API, virtual terminal, reporting tools, hosted payment pages and merchant onboarding portals, causing outages for merchants that depend on it. BridgePay said preliminary forensics showed no card data was compromised.

And in March 2026, the Qilin group claimed an attack on German party Die Linke, with the party warning that staff and internal data could be leaked, a textbook double-extortion play.

Who is affected

  • Organisations holding regulated data (health, financial, personal data), where a leak carries legal and notification costs even if operations recover quickly.
  • Platform and API providers such as payment gateways, whose outage cascades into every downstream merchant or app.
  • Downstream customers and partners, who may be contacted directly by attackers or have their own data exposed.

What it means for developers and engineering teams

The core lesson is that backups solve encryption, not exfiltration. Once data has left your environment, restoring from snapshots does nothing about the leak. Engineering choices that matter most:

  • Exfiltration is a detectable step. Attackers typically stage archives and push gigabytes out over HTTPS or cloud-sync tools. Egress allow-lists for servers, alerts on unusual outbound volume and logging of object-storage reads give you a chance to catch the theft before the encryption.
  • Less data, less leverage. Retention limits, deleting old exports and tokenising sensitive fields (so the database holds references, not raw values) directly reduce what can be used to extort you.
  • Application-level encryption helps. If sensitive columns are encrypted with keys held in a KMS and only the application role can decrypt, a raw database dump is far less valuable.
  • Third-party dependencies are part of your blast radius. The BridgePay outage shows that a single payment provider can take down checkout for many businesses. Design for degraded modes: queue transactions, show clear errors, or fail over to a second processor where the business case supports it.

What to do now

  1. Inventory sensitive data and where copies live: production databases, analytics warehouses, backups, CSV exports, support tooling.
  2. Set and enforce retention for logs, exports and backups that contain personal data.
  3. Restrict and monitor egress from servers and containers; alert on large transfers and on tools such as rclone appearing on hosts.
  4. Encrypt sensitive fields at the application layer with keys in a managed KMS and narrowly scoped IAM roles.
  5. Keep immutable, offline backups and run restore drills, because availability still matters.
  6. Map critical third parties (payment, auth, email, hosting) and document what your app does when each is down.
  7. Prepare breach-notification playbooks, including customer communication, before you need them.

Related on TechLogHub

Sources

Stay Updated

Get the next deep dive in your inbox

Subscribe for product analysis, engineering explainers, and practical guides published on TechLogHub.

See what launched this week

One email a week: new and trending developer tools, fresh comparisons, and what shipped. Unsubscribe in one click.

Multi-Extortion Ransomware: What Engineers Must Know | Evolution Of Ransomware Multi Extortion Ransomware Attacks