Ransomware leak sites turn stolen data into public pressure, and they are often the first place an organisation learns that it, or one of its suppliers, has been breached. This guide explains how data leak sites work as an extortion tool, what government advisories say about the tactics behind them, and how to monitor them safely for your own name and your suppliers' names. It covers how to verify a listing before you act on it, how to triage third-party exposure, and how to measure the programme. It is written for threat intelligence analysts, third-party risk managers, incident responders and privacy teams. It goes deeper than the Dark Web Monitoring Guide and pairs with the Ransomware Data Leak Site Listing Playbook for the response steps.
Key takeaways
- Leak sites are a pressure tool: groups such as Medusa post victims with countdown timers, payment links and offers to sell the data, according to the CISA, FBI and HHS advisory updated in August 2026.
- A listing is a claim, not proof: ENISA warns that the authenticity and currency of leak site claims could not always be verified, and the UK NCSC and NCA say leak site counts can only be taken as an indication.
- Your exposure is often through suppliers: mass exploitation campaigns, such as Cl0p's 2025 Oracle E-Business Suite extortion, list many organisations at once, and your data may sit inside a supplier's listing.
- Monitoring needs rules: use a vetted threat intelligence source rather than browsing criminal sites, agree with legal counsel how stolen data may be handled, and record every alert.
- Paying does not remove exposure: the NCSC and NCA note that paying does not remove a victim's exposure, and data protection liability can arise even if data is never leaked.
How leak sites fit into extortion
A data leak site is a website, usually a Tor .onion service, where an extortion group names victims and threatens to publish, or publishes, their data. It became the standard companion to encryption when groups moved to double extortion: steal data first, then encrypt, then threaten disclosure if the victim restores from backup instead of paying. Some groups dropped encryption altogether.
| Model | What the group does | Example in official advisories |
|---|---|---|
| Double extortion | Exfiltrates data, encrypts systems and threatens to leak | Medusa, Rhysida and Interlock advisories describe double extortion with a Tor leak site |
| Exfiltration-only extortion | Steals data and threatens to publish without encrypting | BianLian shifted to mainly exfiltration-based extortion around January 2023 (AA23-136A); some ALPHV affiliates extorted victims without deploying ransomware (AA23-353A) |
| Mass extortion from one exploit | Exploits one product across many organisations and emails executives | Cl0p's Oracle E-Business Suite campaign in 2025, with listings on its leak site |
| Additional pressure | Calls, emails, printed notes and threats to contact customers or the press | BianLian threatened to send data to clients, partners, competitors and news agencies; Medusa contacts victims by phone or email |
The NCSC and NCA white paper describes how groups choose tactics they think will produce payment, including data-theft-only extortion against sectors such as healthcare. For the business model behind this, see the Ransomware-as-a-Service Business Model Guide and the Data Extortion Without Encryption Guide.
Anatomy of a listing
The Medusa advisory gives the most detailed official description of how a leak site applies pressure. Its .onion site lists victims alongside countdowns to the release of information, posts ransom demands with direct links to cryptocurrency wallets and shows a view count. Victims can pay $10,000 in cryptocurrency to add a day to the countdown, and Medusa advertises the data for sale before the timer ends. Demands are based on the victim's publicly reported revenue, with discounts for quick payment.
| Element | What it tells you | What it does not tell you |
|---|---|---|
| Victim name and logo | The group claims to have attacked this organisation | Whether the claim is true, current or about the right legal entity |
| Countdown timer | When the group says it will publish | Whether it holds anything worth publishing |
| Sample files or screenshots | Evidence to test against your own records | How much data was taken in total |
| Data size claim | The group's statement of volume | Verified volume; sizes are often inflated or include public material |
| Published archive | Data that is now exposed and must be scoped | Whether a copy was also sold privately beforehand |
Why claims need verification
- ENISA's caveat: the ENISA Threat Landscape 2026 states that many cybercrime figures rely on claims on data leak sites and forums whose authenticity and currency could not always be verified, and that leak sites are volatile.
- The NCSC and NCA caveat: leak site victim counts exclude victims who paid and groups that do not use leak tactics, so they are an indication, not a measure.
- Recycled data: ENISA notes that data stolen through fraud or ransomware is advertised on forums and reused in further fraud or ransomware. A "new" listing can contain an older breach.
- Wrong entity: listings often name a brand, a subsidiary or a franchise. The victim may be a supplier or a business with a similar name.
- Affiliate attribution: in ransomware-as-a-service, the affiliate usually obtains and uses the access, not the brand on the site. The NCSC and NCA cite Royal Mail as an attack publicly linked to LockBit but carried out by an affiliate.
A verification checklist
- Confirm the exact legal entity, country and domain named.
- Compare any samples with your data: file names, internal identifiers, dates, document templates.
- Check whether the data matches an earlier known incident at you or a supplier.
- Look for an access route in your own telemetry for the period before the listing: remote access sign-ins, new accounts, unusual outbound transfers.
- Ask the suspected supplier directly, using contractual notification channels.
- Record the outcome (confirmed, supplier, recycled, false) and the evidence.
Building a leak site monitoring programme
- Define the watch list: your legal entities, brands, domains, executive names and your critical suppliers, especially those holding your customer or employee data. Pull suppliers from the third-party register, not memory.
- Choose the collection method: most organisations should rely on a threat intelligence provider or dark web monitoring service that collects leak site listings and sends alerts. Direct collection from criminal infrastructure needs a dedicated, isolated environment, trained analysts and legal approval. See the Dark Web Monitoring Buyer's Guide.
- Agree handling rules with legal counsel: decide in advance whether analysts may download sample or published data, where it may be stored, who may see personal data in it, and how it is destroyed. Take legal advice for each jurisdiction; this guide does not give legal advice.
- Write triage criteria: score each alert by who is named (you, a critical supplier, a minor supplier), what data type is claimed and whether samples exist.
- Connect to response: a confirmed listing about you triggers the incident response plan; a supplier listing triggers the third-party incident process. See the Incident Response Plan Template.
- Pilot and tune: run the watch list for a month, review false positives (similar names, old listings), refine the terms and only then route alerts out of hours.
Choosing a collection approach
| Approach | Suits | Trade-offs |
|---|---|---|
| Commercial threat intelligence or monitoring service | Most organisations, including small teams | Coverage depends on the provider; check which groups and sites are covered and how fast alerts arrive |
| Sector ISAC or national CSIRT sharing | Members of an ISAC, public bodies | Good for sector context; not a complete feed |
| In-house collection | Large organisations with a mature CTI function | Highest control; carries operational security, legal and staff welfare overheads |
| Free public trackers | Awareness and research | No assurance on accuracy or timeliness; never the only source |
Evaluate feeds with the Threat Intelligence Feed Evaluation Guide.
Triage for third-party exposure
When a supplier appears on a leak site, the question is what of yours they held and how they held it.
| Supplier type | Likely exposure | First actions |
|---|---|---|
| Holds your personal data (payroll, HR, CRM, claims) | Employee or customer records | Ask for confirmation and data scope; start a breach notification assessment |
| Has remote access to your systems (IT provider, software support) | Your credentials, VPN profiles, documentation | Disable or rotate their accounts and API keys; review their sessions |
| Integrates by API or file transfer | Tokens, service account credentials, transferred files | Rotate shared secrets and certificates; check transfer logs |
| Holds only commercial documents | Contracts, pricing, correspondence | Assess commercial sensitivity and fraud risk such as invoice redirection |
Where identity fits
Leaked supplier data often contains credentials or the means to get them: VPN configuration files, service account passwords in documentation, API keys in scripts and screenshots of admin consoles. Treat every confirmed supplier leak as a possible credential leak. Inventory the non-human identities that supplier uses with you (API keys, service accounts, OAuth applications, certificates), rotate them and watch for use from new locations. See the Leaked Credential Response Playbook and the OWASP NHI Top 10 NHI3 Vulnerable Third-Party NHI Guide.
Detection and measurement
- Log every alert: date, group, named entity, claimed data, samples, triage score, verification outcome, actions taken.
- Correlate with telemetry: for a listing about you, search for exfiltration to cloud storage (ATT&CK T1567.002) and for remote access anomalies in the weeks before.
- Feed third-party risk: record supplier listings in the supplier risk register so they inform renewal and assurance decisions.
Metrics that show the programme is working:
- Percentage of critical suppliers on the watch list.
- Median time from listing to alert, and from alert to verified outcome.
- Share of alerts confirmed, attributed to a supplier, recycled or false.
- Time to rotate credentials shared with a supplier after a confirmed listing.
- Number of leak site discoveries that came before any notification from the affected supplier.
Framework mapping
| Framework | Reference | How leak site monitoring supports it |
|---|---|---|
| NIST CSF 2.0 | ID.RA-02, DE.CM-06, GV.SC-07 | Threat intelligence received; external service providers monitored; supplier risk managed |
| NIST CSF 2.0 | RS.AN-03, RS.CO-02, RS.CO-03 | Analysis of what happened; stakeholders notified; information shared |
| NIST SP 800-53 Rev. 5 | PM-16 Threat Awareness Program, SR-6 Supplier Assessments and Reviews, SA-9 External System Services, IR-4 Incident Handling, IR-6 Incident Reporting | Programme, supplier oversight and response |
| ISO/IEC 27001:2022 Annex A | 5.7 Threat intelligence, 5.19 to 5.22 supplier relationships | Threat information collection and supplier monitoring |
Decision guidance: respond, wait or engage
- Listing about you, samples match: invoke the incident response plan, preserve evidence, engage legal counsel and consider regulatory notification deadlines. See the Data Breach Notification Checklist.
- Listing about you, no evidence: investigate quietly, prepare holding statements and do not confirm or deny publicly until you know.
- Listing about a supplier: contact the supplier through contractual channels, rotate shared credentials and assess what data they held.
- Engaging the group: any contact with the extortionists is a decision for the incident lead with legal counsel and, where used, a negotiation specialist. Sanctions rules may apply to payment. See the Ransomware Negotiation Guide and the Ransomware Payments and Sanctions Guide.
Small organisations should rely on a monitoring service and their incident response retainer. Large organisations should build the watch list into third-party risk management and run tabletop exercises on a supplier listing as well as their own.
Communicating about a listing
Leak sites are built to be found by journalists, researchers and customers, so a listing can become public before your team has verified it. Prepare for that in advance.
- Holding statement: agree wording that acknowledges awareness of the claim and an active investigation, without confirming or denying data loss.
- Single spokesperson: route all media and customer questions through one channel, so analysts and executives do not give conflicting accounts.
- Staff briefing: warn employees that they may be contacted by the group, as BianLian and Medusa actors have done, and tell them how to report it without engaging.
- Customer and partner contact: where the group threatens to contact your clients, decide whether to tell them first. Early, factual contact usually reduces the damage of a surprise message from criminals.
- Regulators and law enforcement: report to the national authorities as your plan requires; advisories ask victims to report whether or not they pay.
- Keep a timeline: record when the listing appeared, when you learned of it and every decision taken. Regulators and insurers will ask.
Common failure patterns
- Announcing before verifying: confirming a breach because a listing exists, then finding the data belonged to a supplier or an old incident.
- Ignoring a listing because it looks fake: dismissing a claim without checking telemetry for the access route.
- No supplier coverage: watching only your own name while your payroll or IT provider is listed.
- Analysts handling stolen data with no rules: downloading archives to corporate laptops without legal approval or isolation.
- Forgetting credentials: scoping personal data but not rotating the API keys and service accounts the supplier held.
- Assuming payment ends it: the Medusa advisory describes data advertised for sale before the countdown ends, so there is no assurance a paid group did not already sell it.
Lessons from incidents
The Oracle E-Business Suite Exploitation 2025 shows why leak site monitoring must include suppliers and why claims need verification. Executives at organisations running Oracle EBS received extortion emails from the "CL0P team" in late September 2025, sent from compromised third-party email accounts. The attackers had exploited CVE-2025-61882, an unauthenticated remote code execution flaw now in the CISA KEV catalogue, from as early as 9 August 2025, before Oracle's patch on 4 October. By 10 November 2025, 29 alleged victims were listed on Cl0p's leak site and several had confirmed incidents. Organisations that were not themselves listed still had to ask which of their suppliers ran EBS and what data those systems held.
Practitioner checklist
- Build a watch list of your entities, brands, domains and critical suppliers from the third-party register.
- Use a vetted monitoring or threat intelligence service and document its coverage.
- Agree with legal counsel how sample and published data may be handled and stored.
- Define triage scoring and a verification checklist, and record every outcome.
- Link confirmed listings to the incident response plan and supplier listings to the third-party incident process.
- Rotate credentials, API keys and certificates shared with any supplier confirmed as breached.
- Prepare holding statements so a listing does not force an unverified public response.
- Exercise a supplier leak site scenario at least once a year.
Standards and references
- CISA, FBI and HHS: #StopRansomware: Medusa Ransomware (AA25-071A, updated August 2026)
- FBI, CISA and ACSC: #StopRansomware: BianLian Ransomware Group
- FBI, CISA and HHS: #StopRansomware: ALPHV Blackcat
- NCSC and NCA: Ransomware, extortion and the cyber crime ecosystem
- ENISA: Threat Landscape 2026
- CISA: Known Exploited Vulnerabilities Catalog
- NIST: Cybersecurity Framework 2.0
Related NHI Mgmt Group resources: Dark Web Monitoring Guide · Ransomware Data Leak Site Listing Playbook · Data Extortion Without Encryption Guide · Ransomware Groups Guide · BianLian Data Extortion Profile Guide