mythsthe wider recordMaze / Allied Universal2019security

everyone assumed:

with backups, ransomware can't really hurt us

what was actually true:

Backups answer encryption. They do nothing about theft.

how it happened

  1. whoMazeransomware group
  2. the gapbackupsrestored systems fine
  3. the resultdata leakeddouble extortion begins
the gap that let it happen the result

what everyone assumed

The standard ransomware defense is recovery: keep good backups, refuse the ransom, restore. The assumption is that the attacker’s only leverage is locking your systems, which a backup defeats.

what happened

When the company refused, the attackers published a slice of the stolen data on a public site and raised the demand, threatening to release the rest. The backups restored the systems perfectly and did nothing about the copy now in the attacker’s hands, available to leak.

step by step

  1. Maze steals data and encrypts systemsAllied Universal's backups restore everything.
  2. the company refuses to payAbout $2.3 million is demanded.
  3. November 2019700 megabytes publishedThe backups do nothing about the copy in attackers' hands.the assumption breaks here
  4. double extortion spreadsA wave of imitators reshapes ransomware.

how it surfaced

In November 2019 the Maze operators pioneered this double extortion against Allied Universal, leaking 700 megabytes when a roughly $2.3 million demand was refused. The model spread to a wave of imitators and reshaped ransomware.

Backups answer encryption. They do nothing about theft.

Once an attacker has copied your data, restoring your systems leaves the leverage intact, because the data they hold cannot be restored into nonexistence.

picture it at a company like yours

The company here is made up. The other two paths are not: they happened, and each links to the story.

your company
a normal dayYou have good backups and feel ready for ransomware.
the gap nobody seesThe attackers copy your data before they lock anything.one system with no plan B
  1. in this story
    the day it mattersYou restore from backup and refuse to pay.
    what it costs youThey publish your data instead, and backups cannot undo that.
  2. or it goes like this
    howYour main software vendor is hit and goes dark for two weeks.
    what leavessales, orders and invoicingwho ends up with itcompetitors, as customers go elsewhere
    it happenedCDK Global, 2024
  3. or it goes like this
    howBackups live where the attacker can delete them too.
    what leaveseverything, with nothing left to restorewho ends up with itthe business itself, which closes
    it happenedCode Spaces, 2014

sources

  1. Check Point Research, 2020

← all myths

your turn

what you can do about it

  1. this week

    Check what an intruder could copy out, beyond what backups would restore.

    Your ransomware plan probably assumes backups make payment unnecessary. Maze is why that is now half a plan: modern attackers steal before they encrypt. Whether your defenses also reduce what an intruder can reach and copy, not just what they can lock, is the other half.

  2. go deeper

  3. if you're not sure where to start

    Run the offboarding checklist on one leaver. It covers every account and token to close when someone leaves.

    open the checklist →

the letter · every two weeks

one access gap in your inbox, with the fix.

Every issue takes one way access creeps in, shows a real incident where it went wrong, and ends with one thing to check that week. Written for the people who run the tools, without a security team behind them.

  • 1one mechanism, explained plainly
  • 2one real incident, taken apart
  • 3one step you can take on Monday

get the next issue

One email every two weeks. Your address stays here and is never passed to vendors. One click to unsubscribe. Privacy.