Join our Newsletter — 33% off our NHI Course
Home› Glossary› Threats, Abuse & Incident Response› Leakware (Extortionware)
Threats, Abuse & Incident Response

Leakware (Extortionware)

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Threats, Abuse & Incident Response

Leakware, also called extortionware, is malware or a criminal extortion tactic that threatens to publish stolen data unless payment is made. It usually follows unauthorised access, data theft, or exfiltration, and the pressure comes from disclosure rather than encryption. Defences include backup isolation, data loss monitoring, and egress controls.

What Leakware Is and How It Works

Leakware, or extortionware, is a disclosure-based extortion scheme: attackers threaten to publish stolen information unless payment is made. The security significance is that the harm is driven by exposure of data already removed from the environment, so the attacker’s leverage comes from confidentiality loss and reputational pressure rather than system unavailability.

Why Leakware Is Different From Encryption-Based Extortion

Unlike classic ransomware, leakware does not need to block access to files to be effective. It can succeed even when systems are restored quickly, because the attacker still controls a copy of the data and can use timing, sensitivity, or public embarrassment as leverage. That makes the underlying data classification and containment posture central to the threat.

Common Attack Preconditions and Exposure Paths

Leakware usually follows unauthorised access, credential compromise, insider misuse, or exfiltration through exposed services, stolen sessions, or poorly governed third-party access. Once data leaves the environment, the question shifts from preventing encryption to limiting what was taken, where it went, and whether the organisation can prove containment. Defensive visibility around egress, unusual archive creation, and large-scale export activity matters here.

Controls such as segmented backups, egress monitoring, and least-privilege access reduce the chances that a single compromise becomes a disclosure event. For a broader control baseline, many teams map this problem to NIST SP 800-53 Rev 5 Security and Privacy Controls, especially where access control, auditing, and system integrity need to be coordinated.

Detection, Response, and Recovery After Data Theft

Detection focuses on signs of exfiltration, credential abuse, and data staging, not just malware execution. Once leakware is suspected, incident response needs to establish what was accessed, whether the theft is ongoing, and which data sets were exposed so the organisation can make accurate legal, regulatory, and communications decisions.

Because this tactic is usually tied to full attack chains rather than isolated malware, adversary tradecraft mapping is useful. The attack flow described in Anthropic, first AI-orchestrated cyber espionage campaign report is a reminder that recon, credential harvesting, lateral movement, and exfiltration can be chained together quickly when access is already obtained.

Risk and Threat Considerations

Leakware creates a distinct pressure point because the attacker can threaten consequences even after systems are restored. The main risk is not only data loss, but also regulatory exposure, customer harm, and loss of trust when sensitive information is published or credibly threatened with publication.

Failure mechanism: The attacker exfiltrates data, retains proof of access, and uses the prospect of disclosure to extort payment. If the organisation lacks strong egress visibility or data minimisation, the extortion leverage can persist even when endpoint recovery is complete.

Impact: Organisations may face public disclosure, litigation, notification obligations, competitive harm, and downstream abuse of the stolen data for fraud or further intrusion.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-6 — Least PrivilegeLeakware often follows overbroad access that enables bulk data theft.
AU-6 — Audit Review, Analysis, and ReportingDetection depends on reviewing anomalous access and export activity.
Recommendation — Restrict access paths so a single compromised account cannot exfiltrate sensitive data at scale. Correlate audit records to spot unusual data staging and outbound transfer before disclosure occurs.
NIST CSF 2.0PR.DS-01 — Data-at-rest is protectedLeakware targets stolen data, so data protection and minimisation directly reduce exposure.
Recommendation — Protect sensitive data at rest so stolen repositories are harder to monetise and disclose.
MITRE ATT&CKT1041 — Exfiltration Over C2 ChannelLeakware depends on data exfiltration before the extortion phase.
T1020 — Automated ExfiltrationLarge-scale theft is often automated before extortion demands are made.
Recommendation — Hunt for covert outbound transfer techniques that move sensitive data off-network. Detect scripted or automated bulk transfer patterns that indicate data theft at speed.

Practitioner Guidance

Why practitioners should care: Leakware should be treated as a data-exposure event, not only a malware event. That means response ownership needs to span security operations, legal, privacy, and communications so the organisation can assess both technical containment and disclosure consequences.

What to watch for: Prioritise signals of unusual outbound transfer, archive creation, cloud share abuse, or access from accounts that do not normally move sensitive data at scale. If the environment already has a mature control baseline, mapping the response to NIST Cybersecurity Framework 2.0 can help align protect, detect, respond, and recover activities around a disclosure-driven incident.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org