Windows: BlueSky ransomware-related file and share access events

Alerts on Windows file/share access involving .bluesky and "DECRYPT FILES BLUESKY" artifact naming tied to BlueSky activity.

FreeReviewedSigma · High · v5
Product
windows
Service
security
Author
j4son (SigmaHQ), DRL 1.1
Published
2023-05-23
Updated
2026-07-31

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 flags Windows file and share access events where the object name or relative target name matches BlueSky ransomware naming patterns, including files ending with .bluesky or containing the text "DECRYPT FILES BLUESKY". Such artifacts can indicate an active or previous encryption/decryption phase attempted by ransomware. It relies on Windows security telemetry including file access auditing events (4663, 4656) and share access events (5145).

Related detections9 linkedT1486 — drag to rearrange
Malicious JADEPUFFER Lockd Encryptor Execution
Suspicious Mass Locked Extension File Creation by Ransomware
Malicious Interlock Ransomware Encrypted File and Note Creation (via file_event)
Malicious Ransomware Encryption Extension x2anylock
Malicious Fivehands Go Encryptor Execution via Command Line Flags
Malicious SafePay Ransomware Encryptor Command-Line Execution
Malicious The Gentlemen Ransomware Encryptor via Distinctive CLI Flags
Malicious GigaWiper Ransomware File Extension .candy
Malicious Forced BitLocker Encryption for Extortion (via process_creation)
Windows: BlueSky ransomware-related file and share access events
Pivot detection · T1486 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

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