Windows File Creation of .funksec Ransom Note Extension

Flags Windows file creations where the new filename ends with .funksec, consistent with FunkLocker-encrypted file naming.

FreeReviewedSigma · High · v5
Product
windows
Category
file_event
Author
Saiprashanth Pulisetti ( @Prashanthblogs) (SigmaHQ), DRL 1.1
Published
2025-08-08
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 creation events where the target filename ends with the .funksec extension. Appending a distinctive extension to encrypted files is a common ransomware behavior that enables easy identification of affected data and can support extortion workflows. Detection relies on file event telemetry that captures the created/handled filename and allows suffix matching.

Related detections9 linkedT1486 — drag to rearrange
Malicious Remote Encryptor Execution via WMIC Process Call Create (Chaos Ransomware)
Suspicious CyberLock Ransomware Encrypted File Creation
Rhysida Ransomware Encrypted File Extension Created
Phobos 8Base Ransomware Encrypted File Extension Created
Rhysida Ransomware Note CriticalBreachDetected.pdf Created
Possible Akira Ransomware Note or Encrypted Extension Creation
Malicious Storm-2603 Ransom Note File Creation
Possible Ransomware Note or Encrypted File Extension Creation
BitLocker Feature Activation on Multiple Hosts - Native (via bitlocker)
Windows File Creation of .funksec Ransom Note Extension
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.