Malicious RansomHub Ransom Note Creation via README Random Suffix Pattern (via file_event)

PremiumReviewedSigma · High · v1
Product
windows
Category
file_event
Author
HuntRule
Published
2026-09-25
Updated
2026-09-25

ATT&CK techniques

Impact
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

What it detects

This rule detects creation of RansomHub ransom note files following the README_ prefix with a random six-character suffix documented by Group-IB. Adversaries drop these notes across encrypted directories to signal impact and deliver extortion demands, so their appearance indicates active ransomware encryption.

Related detections9 linkedT1486 — drag to rearrange
Malicious Ransomware Payload Execution via HWP Word Processor Spawning Executable from Temp
Suspicious javaw.exe Executing JAR From Masqueraded Roaming Directory via Interlock Ransomware (via process_creation)
Malicious NailaoLocker Ransom Note and Encrypted File Creation (via file_event)
Malicious Ransom Note and Encrypted Extension via Hakuna Matata Variant (via file_event)
Malicious Hunters International Ransomware Execution via rundll32
Malicious WannaCry Decryptor Launching Tor via process_creation
Malicious WannaCry tasksche Execution from mssecsvc Service via process_creation
Malicious Shadow Copy Deletion and Recovery Inhibition via process_creation
Suspicious EKANS Ransomware Payload Dropped to Drive Root (via file_event)
Malicious RansomHub Ransom Note Creation via README Random Suffix Pattern (via file_event)
Pivot detection · T1486 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.