Skip to content
[ SIGNAL VERIFIED ] INDEPENDENT CYBERCRIME JOURNALISMCLASSIFIED // THE UNDERGROUND HAS A NEWSROOM / RSS
.COM
Latest News
ALL NEWS
Newsroom

From Maze to n0n: How Darknet Leak Sites Turned Data Claims Into Extortion

A sourced history of darknet extortion leak sites, from Maze's 2019 double-extortion model to data-only threats in 2026, with clear evidence and privacy limits.

Newsroom editorial artwork
Darknet FilesConfirmed / documentedEvent / disclosure: 2019-11-01Last editorial review: 2026-11-21Region: International

IPCRIME | Darknet Files | History reviewed November 21, 2026. By the late 2010s, cyber-extortion groups increasingly used public humiliation and the threat of publishing stolen files alongside ransomware encryption. These dedicated leak sites became part of underground crime’s information economy: a place to assert possession of data, set deadlines and create pressure through publicity. This historical account explains how the practice emerged, why leak-site claims require skeptical analysis and how the model has shifted toward data-only extortion.

Before and during Maze, 2019–2020

Mandiant’s research on Maze describes ransomware deployed in targeted incidents from at least May 2019 and a later model in which attackers stole files and threatened to publish them. From November 2019, researchers observed the pairing of extortion through public data exposure and a ransomware service operated by multiple actors. Group-IB and Unit 42 identify Maze’s dedicated leak site as a highly visible early example of this approach. It was not necessarily the invention of extortion through data theft, which predates this era.

Why publishing a company name became leverage

An encryption event threatens availability. Publishing stolen records threatens confidentiality, reputation, customers and regulatory obligations. A leak-site entry can try to create urgency before an affected organization completes forensic work. Some operators present countdowns, sample files or inflated record totals, while others make unsupported claims. This practice exploits the fact that the public cannot easily distinguish a genuine private dataset from material gathered elsewhere.

Different forms of pressure are not equivalent

In some documented incidents, attackers encrypted systems after copying files. In others, criminals threatened exposure without any confirmed encryption at the named organization. Public reporting often calls both ‘ransomware’, but they have different technical and recovery consequences. A company may have to investigate vendor-held marketing data, for example, without there being evidence of an intrusion into its own payment systems. That distinction is central to IPCRIME’s Underground Watch.

Leak-site data as an uncertain measurement

Unit 42’s published leak-site studies examine criminally posted information as a source of trends, while also limiting conclusions to the monitored sources and time period. A list of ‘victims’ can include repeated names, companies mentioned because their supplier was breached, outdated incidents or alleged compromises without corroboration. Listing counts therefore measure a public criminal pressure tactic, not automatically the number of confirmed breaches, distinct people harmed, or successful ransomware deployments.

The 2026 n0n case shows the newer pattern

In 2026 a group using the name n0n attracted attention for rapid extortion postings. Reports from Reuters confirm limited third-party vendor exposures involving financial-sector marketing data, but could not verify all the operator’s purported stolen files. Threat-intelligence firms have also differed on how much evidence of encryption they could establish in n0n cases. The important historical connection is not that n0n is the same as Maze; it is that public data claims can apply pressure independently of a demonstrated encryptor. See IPCRIME’s n0n evidence analysis.

How an independent newsroom should report it

  • Attribute allegations to the group or researcher making them; do not call a listing a confirmed compromise.
  • Look for an affected organization’s statement, regulator filing, reliable investigation or court finding before describing what happened as established.
  • Do not republish private data or provide operational access to criminal sites.
  • Do not convert arrest totals, claim counts or record volumes into unverified unique-victim figures.
  • Preserve relevant civil-liberties distinctions: privacy networks have lawful uses, and using encryption or Tor is not proof of criminal activity.

Sources and methodology

Mandiant: Maze tactics and field investigations, July 2020; Unit 42: leak-site data analysis and historical context; Group-IB: dedicated leak sites explained; Reuters: November 2026 vendor claims and confirmations.

Historical evidence limits

Mandiant documented Maze ransomware campaigns in 2019 that paired encryption with threats to publish stolen files. Unit 42 and Group-IB describe how dedicated leak sites became a common way to pressure victims. A 2026 n0n example illustrates that a leak site can publicize data-theft allegations even when deployed file encryption is not established in every claimed case. A post on a criminal website is evidence of what a group claimed, not independent proof of the data’s provenance or of culpability.

No contemporary source provides a complete census of every underground extortion listing, and apparent victim counts depend on collection dates, deduplication and whether cases were independently corroborated. Current-market availability, specific hidden-service addresses and stolen files are intentionally excluded. Actor attribution and individual criminal liability must not be inferred solely from a page branded with a group name.

Original research-based history. IPCRIME did not access an extortion marketplace or recover stolen files for this article. All current-source citations lead to public reporting and defensive research, not to hidden services or stolen datasets.

Editorial note

IPCRIME distinguishes public records and documented findings from allegations, analysis and commentary. Report corrections through our contact page.