Join our Newsletter — 33% off our NHI Course
Threats, Abuse & Incident Response

Ransomware Note

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

A ransomware note is a message left by an attacker after encrypting or stealing data, usually demanding payment and giving contact or payment instructions. It commonly appears as a text file, image, wallpaper change, or login screen message and is part of the extortion workflow, not the malware itself.

What a ransomware note is doing in the attack flow

A ransomware note is not just a message, it is part of the extortion workflow. It tells the victim that encryption, theft, or both have occurred and typically pushes them toward payment, contact, or negotiation steps. Because the note is the attacker’s communication channel, it often signals that an incident has moved from access into coercion.

Different families use different delivery styles, but the purpose is consistent: to create urgency, control the victim’s next move, and reinforce the attacker’s leverage. Notes may appear as files on disk, modified wallpapers, or login-screen messages, which makes them highly visible even when the underlying malware has already finished its work.

Why the note matters to incident response

The note is often one of the first artifacts responders see, but it should be treated as evidence rather than the root problem. It can help confirm that the event is ransomware-related, indicate whether the attacker claims data theft, and preserve clues about the actor’s messaging or payment workflow. For broader context on current ransomware tradecraft and published threat trends, see CISA cyber threat advisories and ENISA Threat Landscape.

A note can also help distinguish simple encryption from double extortion, where attackers threaten to leak stolen material. That difference affects containment priorities, legal review, and communications because the response is no longer only about restoring systems, but also about understanding what data may have been taken.

How ransomware notes are used to pressure victims

The note is designed to influence behaviour. Attackers use it to create time pressure, direct the victim to a payment mechanism, and discourage immediate remediation by implying that files will be deleted, leaked, or made unrecoverable. In some campaigns, the note also acts as a contact portal for negotiation, which lets attackers manage the incident like a business transaction.

Because the note is visible to users and executives alike, it can shape the organisational response before technical teams have fully assessed scope. That makes the note strategically important even though it is not the malicious code itself.

What to look for after a ransom note appears

The note should prompt a broader check for scope, not a narrow focus on the message itself. Teams usually need to determine which hosts were affected, whether the attacker still has active access, whether backups are safe, and whether exfiltration occurred. The note is one artifact among several, alongside logs, endpoint evidence, and any indicators of lateral movement or staged data theft.

Do not assume the presence of a note means the attack is complete. In many incidents, the note appears after the attacker has already established persistence, harvested credentials, moved laterally, or prepared for follow-on extortion.

Risk and Threat Considerations

Ransomware notes matter because they mark the transition from covert compromise to overt extortion, and they often coincide with encryption, data theft, or both. The visible note can also distract defenders from the larger compromise, especially when attackers want to create urgency and delay containment.

Failure mechanism: The attacker uses the note to confirm impact, pressure payment, and mask the real incident scope, while the underlying intrusion may still be active elsewhere in the environment.

Impact: Organisations can face extended downtime, data exposure, negotiation pressure, and a delayed understanding of how far the compromise spread.

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 CIS Controls v8 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKT1486 — Data Encrypted for ImpactRansomware notes usually accompany data encryption for impact and extortion.
T1490 — Inhibit System RecoveryRansomware notes often accompany recovery suppression and backup disruption.
Recommendation — Map the note to encryption-for-impact activity and hunt for the preceding intrusion path. Check whether recovery mechanisms were impaired before restoring systems.
CIS Controls v8CIS-17 — Incident Response ManagementA ransom note is an incident artifact that should drive containment and evidence handling.
Recommendation — Use incident response procedures to preserve evidence and coordinate containment.
NIST CSF 2.0RS.MA-01 — Incidents are contained, eradicated, and recovered fromThe note marks an incident state that requires containment and recovery actions.
RC.RP-01 — Recovery plan is executed during or after a cybersecurity incidentThe note is a trigger for executing recovery plans after ransomware impact.
Recommendation — Contain the affected environment and restore operations through a controlled recovery process. Execute the recovery plan once the ransomware impact is confirmed.

Practitioner Guidance

What to watch for: Treat the note as a starting point for incident scoping, not as proof that the response can wait for negotiation. Preserve the exact text, image, filenames, and timestamps because they may support attribution, campaign comparison, or later forensic reconstruction.

Practitioner takeaway: The note is evidence of extortion intent, but the real response priority is to determine what else the attacker touched before the message appeared.

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 3, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org